Oroko logoOroko
See clearly. Understand better.

Map how work actually happens.

Oroko is a structured, canvas-first process mapping tool. Capture a process once — the map, the procedure, the analysis and the sign-off all come from the same record, not four separate documents.

No infinite whiteboard. No BPMN modeller. Just the process, structured.
Every step carries an owner, a system and a role — not just a box and a line.
Oroko
Oroko canvas showing the Customer Onboarding process map with the Qualification step selected and its inspector panel open

Real screenshot from the Oroko prototype — the Customer Onboarding map, current state.

Built for

Operations teams Transformation & delivery Consulting & advisory Product & implementation Compliance & governance

The process data is the product. The canvas is just the way you see it — change a step once, and the procedure, the analysis and the sign-off all change with it.

Most process tools make you keep the diagram, the SOP and the risk log in sync by hand. In Oroko they're the same record, viewed three different ways.

One process, many outputs

More than a diagram.

Capture the process once, then use the same structured information for analysis, future-state design, implementation context and operating procedures.

01

Structured mapping

Map activities, decisions, owners, systems, inputs and outputs without wrestling with shapes and lines.

02

Contextual analysis

Attach pain points, risks, assumptions, dependencies and open questions to the exact step they relate to.

03

Current and future state

Duplicate a process and redesign it with a clear view of what's changing and why.

04

Procedure generation

Turn the map into a clean operating guide without rewriting the same process in another document.

05

Governed systems & roles

Owners, roles and systems are managed centrally — add a new one from the canvas, reuse it everywhere.

06

Portable by design

Import and export JSON so processes can be saved, reused, migrated or generated externally.

Generated, not re-typed

Reads like a document your team will actually use.

Every procedure is generated straight from the map — numbered steps, owners and flagged issues, formatted to read like a real operating document instead of an exported diagram.

  • Stays connected to the map — edit a step, the document updates itself
  • Flagged issues appear as inline highlights, not buried in a separate report
  • Click straight through to the exact step on the canvas, and back
Screen recording of the Oroko prototype: browsing the Process Library, opening Customer Onboarding, viewing the Qualification step, then switching to the generated Procedure and Analysis pages

Actual interaction, recorded from the prototype — Library → Map → Procedure → Analysis.

Progressive depth

Simple first. Powerful in layers.

A user should be able to map a process in minutes. When the work demands more, Oroko reveals analysis, solution, delivery and governance layers without making the core experience heavy.

01
Flow layerWhat happens and in what order.
02
Operational layerOwners, systems, inputs, outputs and supporting context.
03
Analysis layerPain points, delays, risks and improvement opportunities.
04
Solution and delivery layersRequirements, scope, acceptance criteria and implementation readiness.
05
Governance layerOwnership, approvals, review dates and version history.
Work the way you need

One core product. Different working modes.

Use the same structured foundation for current-state discovery, future-state design, process improvement, standard operating procedures or system implementation.

Current-State Discovery

Capture the process live during a workshop or discovery session.

Future-State Solution Design

Show the improved process, responsibilities and system actions clearly.

Standard Operating Procedure

Publish the final approved process as a guided operating reference.

About Oroko

Built to make work easier to understand

Oroko began with a simple idea rooted in Korokoro, the Urhobo word behind its original concept: see clearly.

Too many important processes live across conversations, documents, spreadsheets and disconnected diagrams. Teams may know that work is getting done, but not always how it moves, who owns each step or where the friction sits.

Oroko is being built to change that.

It gives teams one structured place to map how work happens, capture the operational detail behind each step and turn that understanding into procedures, analysis and improved future-state processes. The goal is not to create another complicated diagramming tool. It is to help people move from scattered information to a clear, shared understanding of the work.

Why we're building it

We believe process tools should support the conversation rather than slow it down. A user should be able to map a process during a workshop, add the right context as they learn more and produce useful documentation without rebuilding the same information in several different tools.

That's why Oroko is designed to be:

  • Simple enough to use from the first step
  • Structured enough for professional work
  • Visual without becoming an infinite whiteboard
  • Detailed without making the canvas feel crowded
  • Useful across discovery, operations, redesign and governance

Designed to feel calm, clear and professional.

Explore the redesigned Oroko app prototype and test the interaction model.

Open the prototype →