
📋 Business Analysis & Process
Swimlane process maps, customer journey maps and prioritisation matrices for business analysts. Open any template to see the finished diagram, then use it as the starting point for your own in the Studio.
25 templates
Who does what when a bank approves a personal loan: the customer, the loan officer, the credit team and operations, with the rework loop for missing documents.
The purchase cycle from an employee's request to paying the vendor, across the requester, the manager, procurement, the vendor and accounts payable.
How a new joiner is onboarded across HR, the hiring manager, IT and the employee, from signed offer to a productive first week.
A car insurance claim from accident to settlement, across the policyholder, the insurer's claims desk, the surveyor and the garage.
From a customer's order to cash in the bank, across sales, credit control, the warehouse, logistics and finance.
An ITIL-style incident flow across the user, the service desk, the support team and the problem manager, with escalation for major incidents.
A planned in-patient stay from admission to discharge across the patient, the front desk, the doctor, the nurse and billing, including insurance pre-authorisation.
A product return from request to refund across the customer, customer support, the courier, the warehouse and finance.
How a change to a production system is requested, assessed, approved by the change board, built, tested and released.
Adding a new supplier: the vendor, procurement, compliance (KYC and GST checks) and finance, from registration to an active vendor code.
A customer opening a savings account online, from comparing banks to the first transaction, with the video KYC step as the main pain point.
A shopper ordering groceries on a quick-commerce app, from search to unpacking, showing where substitutions and late slots hurt satisfaction.
A patient's visit to a multi-speciality clinic, from booking to follow-up, highlighting long waits and paperwork as the pain points.
A student applying to college, from shortlisting to the first day, with document verification and fee payment as the friction points.
A new user's first two weeks on a B2B SaaS free trial, from sign-up to paying, to find where trial users drop off.
A policyholder's experience of a health insurance claim, from hospital admission to reimbursement, showing where uncertainty and waiting hurt.
A customer ordering dinner on a food delivery app, from choosing a restaurant to eating, showing how delays and cold food affect the rating.
A traveller's day flying domestically, from booking to reaching the destination, with security queues and baggage wait as low points.
What joining a company feels like for a new employee in the first 30 days, to improve onboarding from the employee's side.
A home customer getting a new broadband connection, from choosing a plan to stable internet, with the technician visit as the key moment.
A mobile banking app backlog placed on an impact-vs-effort grid, separating quick wins like UPI autopay from big bets like loan pre-approval.
Ideas to raise an online store's conversion rate, ranked by expected impact and effort, from one-page checkout to a loyalty programme.
HR improvement initiatives ranked by impact on employees and effort to deliver, from digital onboarding forms to a new HRMS.
Digital projects for a hospital ranked by patient impact and effort, from online appointment booking to a full EHR migration.
Customer feature requests for a B2B SaaS product ranked by impact and effort, to decide what goes into the next release.
More Business Analysis & Process templates are being added regularly.
Business analysts use diagrams to agree how work happens today and how it should happen tomorrow: process flows and swimlanes for the as-is and to-be process, use cases for requirements, and journey maps for the customer view.
These templates help in requirement workshops, in BRD and FRD documents, and when explaining a change to stakeholders who will not read a long specification.
A swimlane process diagram, with one lane per team or role. Draw the as-is first, then a second version where the removed steps and new automation are easy to compare.
Use a context or use case diagram near the start to set scope, process flows for each business process, and sequence diagrams for system interactions in the functional sections.
Yes. Every diagram has Executive, Standard and Extreme views, so sponsors see the main path while the delivery team sees every step and exception.