One Zoomable Blueprint of Who Does the Work, What They Do, and What They Use
Understand which jobs your systems and features actually serve, which solutions they compete with — and what breaks when you deprecate one.
Interview the people doing the work and map how production really happens — line, station, and the tools at each one. Then find the waste.
See the frontstage touchpoints your customers experience against the backstage systems that deliver them, drawn on one canvas.
Document how delivery actually works, per client, without spending the engagement on documentation. Reuse the model on the next one.
Map patient flow or shipment flow across the roles, equipment, and systems it passes through — including the handovers where it goes wrong.
Map every critical function to the roles, systems, and third parties that run it — the register DORA, NIS2, and ISO 22301 expect, derived from the model instead of maintained by hand.
Your service runs across many people, tools, and handoffs. You can feel where it hurts — but no document, board, or head holds the whole picture.
Process docs sit in one tool, research in another, and the real flow lives in people's heads. Nobody can say which flows a system actually touches.
Documenting how the work runs today takes so long that it rarely gets done — and it's outdated before it's finished.
Duplicated tools, dead steps, single points of failure — without the whole picture they go unseen, and every chance to fix them goes with them.
In RoleDream it's one resource, connected to every job that uses it. A diagram shows what somebody drew; a model answers questions you didn't think to ask — and getting one shouldn't take an enterprise suite, a consultant, and a year of rollout.
You can't query a diagram.
Every resource is staged under the step that uses it. From that single link RoleDream derives the whole dependency picture — read it from either end, with nobody maintaining it by hand.
Before you change or retire a resource, see every job that depends on it — including the ones owned by teams you'd never think to ask.
Find the critical systems half your operation quietly runs on — and the single points of failure behind them. For teams under DORA, NIS2, or ISO 22301, this same lookup is the critical-function mapping the regulation asks you to keep.
Spot duplicated and underused tools across teams — the waste no single team is positioned to see.
Connect any AI assistant that speaks MCP and the whole cycle runs as a conversation. The assistant is taught the model itself, so what it creates lands correctly on the canvas.
Hand it an interview or a process document — it creates the roles, jobs, steps, and resources, fully linked.
Review the AS-IS — how the work really runs today — and find the pain and the waste.
Design TO-BE solutions right beside the current ones — same jobs, better flows, compared on one canvas.
A well-described TO-BE flow is already close to a specification — generate a prototype straight from it.
"Here's my interview with Maria. Map it to the Blueprint — roles, segments, jobs, solutions with steps, and the tools they use. Tag everything as-is."
"Looking at the AS-IS for 'Order food for delivery' — where is the waste? Which steps could be merged or removed?"
"What jobs and solutions does the Payment gateway touch? We plan to replace it."
Works with whichever MCP-capable assistant or CLI your team already uses — one-time setup, then it's a conversation.
The free tier is enough to map your first flow. Start free, upgrade anytime.
Everything that makes the map trustworthy: the evidence behind it, the objects underneath it, and the team keeping it current.
Link interviews, observations, and test results to the jobs they support — the map keeps its receipts.
Universal links connect any two objects, both ways. Open any solution and see its jobs, steps, resources, and the research behind it — no dead ends.
Your team sees changes as they happen, so the map stays the thing everyone argues from — not the diagram nobody updated since kickoff.
RoleDream is inspired by Service Design, Jobs-to-be-Done, and classic process mapping — unified into one model that gives you the strengths of each without asking you to adopt any of them.
Choose the plan that fits your team. Start free, upgrade anytime.
Pro is priced per billable user — Viewer (read-only) members are always free, so you can invite your whole organization to read the map at no extra cost. Save 20% with annual billing.
Your data is encrypted in transit and at rest. Verified technical controls aligned with:
Everything you need to know about RoleDream.
Three things, as one connected model: who does the work (roles and the groups they serve), what needs doing (the stable jobs, and the competing solutions currently hired for them), and what the work runs on (every tool, system, document, and piece of equipment, staged under the exact step that uses it). It's process mining for human work — instead of reading system logs, you capture how people really operate from documents, interviews, and observation.
A diagram is a picture of what somebody drew. RoleDream is a model you can query. Draw the same system in five Miro boards and you have five disconnected shapes that nothing keeps in sync. In RoleDream it's one resource, linked to every job that touches it — so "what breaks if we replace this?" has an answer, and the answer stays right as the map changes. Those are the questions a board can't answer.
Those suites also model processes rigorously — but they're built as enterprise rollouts: consultant-led implementations, modeling notation to learn, enterprise pricing. RoleDream sits in the gap between them and the whiteboard tools: a queryable who/what/how model you get self-serve. Sign up, hand your AI assistant an interview or a process document, and have your first map the same day — no notation, no rollout project.
No. JTBD is one of the three traditions the model unifies, alongside Service Design and plain process mapping. If you just want to document how a process runs and what it depends on, the same objects and links carry that perfectly well — you can use the framings or ignore them entirely.
Jobs are stable goals — "deliver order" doesn't change. Solutions are the concrete ways to do them, and they compete: "deliver by car" against "deliver by drone", each with its own steps, resources, and trade-offs. You don't hire a job; you hire a solution for it, and you fire it when something better comes along. Hiring decisions record every switch and the reason behind it, so the map builds a history of what actually works.
Under every step, resources stage into two lanes: Frontstage above the line of visibility — what the customer can see, like an app screen or a service counter — and Backstage below it, the systems and tools working behind the scenes. It's the classic service-blueprint line of visibility, drawn natively on the canvas instead of annotated on top of a diagram.
RoleDream runs a hosted MCP server, so it connects to any AI assistant or CLI that speaks the Model Context Protocol — you keep whichever one your team already uses. Setup is a one-time OAuth authorization. What makes it work isn't the connection but the briefing: the assistant is taught the model itself, so it separates real jobs from tool complaints, keeps individual roles apart from groups, and stages resources under the right steps. Paste an interview transcript or a process document into the chat and you get a draft to review, not a pile of objects.
That's the normal case, and it's the point. Most source material is messy — activities, complaints about tools, half-remembered process. You don't need to clean it up first: hand over what you have, and the assistant drafts a mapping for you to correct. Expect a handful of real jobs per role with plenty of steps and evidence underneath them. Start with one role or one flow, get it right, and grow from there.
Yes. Those regulations ask you to map critical functions to the roles, systems, and third parties that keep them running — and that chain is exactly what the model holds: jobs broken into steps, each step staged with the resources it depends on and the roles responsible. Because it's a queryable model rather than a drawing, the mapping stays current as operations change, and "which functions does this system support?" always has an answer you can export for an audit.
Yes. Your data is encrypted in transit and at rest. RoleDream maintains SOC 2 readiness and ISO 27001 alignment with continuous real-time monitoring. We follow GDPR-compliant data handling practices. View our Security Audit Report for details.
Map the AS-IS, design the TO-BE beside it, and find the waste in between.