Method
How we take a process apart — and put it back together.
No gut feel — a repeatable method. Here's how we work and the standards we model in.
How we work
The method, step by step.
Four phases — Diagnose, Design, Build, Handover — across seven concrete steps. Every step produces a result you can see and check before the next one begins.
- 01
Diagnose
Scoping
We draw the boundaries: where does the process start, where does it end, who's involved? A clearly bounded slice instead of “the whole company” — that's what makes the result concrete and the mapping reliable.
- 02
Diagnose
Current-state capture
We talk to the people who run the process every day and watch it where it actually happens. The real workflow is rarely in the manual — it lives in shouted requests, workarounds and Excel files.
- 03
Diagnose
End-to-end mapping
We make the whole flow visible — from the triggering event to the outcome, across every department and system. Only once the process is on a single sheet can you see the handoffs where it jams.
- 04
Diagnose
Bottleneck & cost analysis
We quantify where waiting time, duplicated work and re-keying between systems arise — and what they cost. The critical path is named, not guessed, and the levers are prioritised by impact.
- 05
Design
Target-state modelling
We design the target process — cleanly documented and specified in established notation. Responsibilities, systems and data flows are pinned down so it's clear what gets built before anything is built.
- 06
Build
Implementation
We build the solution: integration, automation, tooling. Named technologies instead of buzzwords — and a workflow that demonstrably runs, not just a slide deck.
- 07
Handover
Handover & enablement
We train your team and hand over the documentation. The solution should keep running long after we've left the building — operation and upkeep stay in your hands.
Notation & standards
We model in established standards.
No home-made box-and-arrow diagrams. We work in notations your team, your IT and any successor can read — today and in five years.
The established notation for business processes. Events, tasks and decisions are represented unambiguously — readable for the business side and IT alike.
A view of the entire material and information flow. We separate value-adding from non-value-adding steps and make waiting times and inventory visible.
The process laid out in lanes per role or department. The handoffs between lanes are exactly where responsibility — and information — gets lost.
Who does the work, who's accountable, who's consulted, who's informed? A clear matrix ends the question “who was actually responsible?”.
Supplier, Input, Process, Output, Customer — the frame we use to bound a process cleanly before mapping it in detail.
From practice
A look at a real artefact.
This is what an interim result looks like. The example below is deliberately anonymised and redacted in places — it shows the craft, not any specific client's data.
The difference
Why this is different from a consulting report.
The classic consulting engagement ends with a presentation. Ours ends with a process that runs. Modelling and building are the same hand — that's the whole difference.
The classic consulting report
- Ends with a PDF presentation and a list of recommendations.
- Describes what ought to be done — the doing stays with you.
- Often stays at the buzzword level, without naming concrete systems.
- Disappears into a shared drive after the final presentation.
Working with taktforge
- Ends with a running process your team uses the very next day.
- Models and builds from one hand — the same people, no handover break.
- Names technologies, systems and integrations concretely — and builds them.
- Leaves documentation and a trained team behind, not just an invoice.
Free consultation
Let's talk about a process that's costing you money.
30 minutes, free, no strings attached. You describe the workflow that's stuck — we tell you honestly whether and how we can help.