The Workflow Nobody Mapped
Distribution advantage often hides in an unglamorous customer workflow that incumbents consider beneath the product.
The brief named the transaction. The durable system lived in the work around it — the step everyone apologised for and nobody claimed.
A marketplace or B2B tool fights on features and price. Meanwhile the customer’s real job includes a messy side-process: scheduling, compliance paperwork, collecting residuals, reconciling invoices, chasing a signature.
Many durable platforms won by owning the annoying workflow that sat beside the obvious one. They became the system of record for a job the incumbent never wanted to see.
HACKERS studies the adjacent job. Own the unloved step, become habitual, earn the core transaction. Then refuse to become a tollbooth: export, open data, a path off.
The brief names the transaction. The system lives in the work around it. The wedge is the step everyone apologises for.
This is not a feature war. It is a day-in-the-life war.
A marketplace or B2B tool fights on features and price. Meanwhile the customer’s real job includes a messy side-process: scheduling, compliance paperwork, collecting residuals, or reconciling invoices.
Incumbents defend the stage. Challengers move into the wings.
The core transaction is photogenic: the sale, the booking, the trade. The adjacent job is embarrassing: the spreadsheet after, the PDF, the phone call to a person who does not use the product.
Incumbents treat that work as ‘not our product’. That sentence is a gift. It tells you where they will not follow until it is too late.
Owning a workflow can become a tax on leaving. The ethical test is whether the customer is more capable than before, and whether exit remains possible.
Name the false object, then drop it.
C1
The transaction is the job
Roadmaps mirrored the checkout.
The job includes everything that makes the checkout possible and surviving.
C2
Ugly is unstrategic
Paperwork was beneath the brand.
Ugly is where habit lives.
C3
Features win
A comparison matrix was the strategy.
A system of record for an adjacent job beats a prettier matrix.
C4
Capture is product
Lock-in treated as moat.
Usefulness should not require captivity. Export is a control.
C5
The user is the buyer
Procurement spoke for the day.
Shadow the person who does the apologised step.
What actually sat on the table.
If we win the core transaction, the rest of the workflow will follow. The ugly adjacent job is not our product.
Feature matrices are written by people who attend demos. Adjacent jobs are visible only to people who stay for the hour after the demo, when the spreadsheet opens.
The chain reaction is habit, then record, then the photogenic transaction following usefulness. Skip export and the chain reaction is resentment.
Do not study the outfit.
A beautiful checkout is a costume. So is a category narrative. The interesting object is the spreadsheet that still runs after the demo.
If your case study stops at ‘they built a better marketplace’, you have a press release. The studio begins when you can name the step the incumbent was too proud to touch.
Many durable platforms won by owning the annoying workflow that sat beside the obvious one — becoming the system of record for a job the incumbent never wanted to see.
Pretty txn, no habit
Demo-ware. Churn waiting to happen.
Ugly step, no record
A gadget. Useful once.
Habit, hostage files
Looks like a moat. It is a hostage situation.
Habit, exportable record
The only cell that should scale.
S0 Feature matrix
pitch 80 / habit 20
S1 Core txn win
pitch 90 / habit 35
S2 Wedge on the ugly
pitch 40 / habit 60
S3 Daily use
pitch 55 / habit 80
S4 System of record
pitch 70 / habit 90
S5 Ethical exit
pitch 60 / habit 95
Export works. Moat is usefulness.
A1
Map the day
The transaction is one scene. The job is the day.
A2
Apology is a pointer
The step people apologise for is the wedge.
A3
Ugly compounds
Habit forms where the work is frequent and unloved.
A4
Record last
Become the system of record after you are useful, not by trapping files.
A5
Exit is proof
A customer who can leave and stays has given you a real grant.
P1 Day
What actually happens between alarms?
Personas that never shadow a Tuesday.
P2 Wedge
Which apologised step can you own in 90 days?
Boiling the ocean of the full suite.
P3 Record
What truth must persist?
Becoming a file dump without a job.
P4 Exit
How does the customer leave whole?
Formats that only your product can read.
| ID | Failure | What broke | Control |
|---|---|---|---|
| F1 | Checkout myopia | The roadmap was the payment flow. | Shadow the day. Budget the wings. |
| F2 | Suite cosplay | A full platform announced before a wedge. | One unloved step, done obsessively. |
| F3 | Buyer not user | Procurement’s pain was not Tuesday’s pain. | The apologiser is the design partner. |
| F4 | Hostage files | Data gravity used as a weapon. | Export on day one. Earn gravity with usefulness. |
| F5 | Incumbent disdain | Ugly work treated as low-status. | Low-status work is often the load-bearing wall. |
| F6 | Habit without ethics | Daily use became a trap. | Capability up, switching costs down. |
Accounting after the sale
The invoice is the real product.
Whoever owns reconcile owns the relationship.
Clinical admin
The EHR fight is often about notes, not diagnosis.
The adjacent job is the record. The medicine is the costume.
Devtools
CI, not the editor, became the system of record.
The unloved pipeline step was the wedge.
Logistics docs
The bill of lading, not the truck.
Paperwork is the interface. Trucks are vehicles. See File OPS-04.
Map the day, not the transaction. The wedge is the step everyone apologises for.
Own the unloved step → become habitual → earn the right to the core transaction → raise switching costs ethically through usefulness, not lock-in tricks.
01 Shadow
One real day. Note every apology.
02 Pick the wedge
The frequent, unloved, unclaimed step.
03 Do it obsessively
Do not announce a suite. Finish the step.
04 Become the record
Persist the truth of that job.
05 Earn the core
Let the photogenic transaction follow usefulness.
06 Export
If they cannot leave, you did not win. You occupied.
- Roadmap mirrors the competitor matrix.
- Ugly work is out of scope.
- Buyer speaks for the user.
- Data gravity is a strategy slide.
- Success is winning the photogenic txn.
- Roadmap mirrors a shadowed Tuesday.
- The apology is the spec.
- The doer is the design partner.
- Export is shipped.
- Success is being the record people choose.
R0 Step
One apologised task still lives in a spreadsheet.
R1 Day
The product is opened for that task.
R2 Team
Colleagues follow the record.
R3 Firm
The core transaction migrates.
R4 Market
Incumbents still ship features for the photogenic step.
R5 Exit crisis
If export was skipped, the firm is trapped and resentful.
| Topic | Typical brief | HACKERS studio |
|---|---|---|
| Strategy | Positioning and category design. | Shadow a Tuesday. The category is a costume. |
| UX | Flows of the happy path. | The apologised step is the happy path in disguise. |
| Moats | Network effects and brand. | Habit around an unloved job, with export. |
| Sales | Buyer personas. | The user who does the ugly work can veto the renewal. |
| Ethics | Dark patterns as a don’t. | Hostage data is a dark pattern with a board slide. |
Elite programmes still stop at the object.
Product courses still start with the job-to-be-done as a sentence the founder already liked. Strategy courses still start with the industry’s photogenic transaction. The adjacent job is ‘operations’ — a word used to mean ‘someone else’.
HACKERS makes the apology the brief. SCAN the day. FLIP the feature matrix. BUILD the unloved step. BREAK your own lock-in with an export test. PROVE habit with a Tuesday, not a demo.
Owning a workflow can become a tollbooth. The test is whether leaving remains possible and whether the customer is more capable than before.
Do not admire the turning point. Redesign the join.
Shadow a customer for one real day. Which step do they hate that no vendor claims? That is the wedge.
Shadow a customer for one real day. List every step they apologise for.
Which of those steps has no vendor that claims it with pride? That is the wedge.
Design a 90-day product that only does that step, obsessively.
What truth must persist for that step to become a system of record?
Write the export. If you flinch, you were building a tollbooth.
Have you watched a Tuesday, or only a demo?
Demos are costumes. Tuesdays are systems.
0–8h
Shadow
One Tuesday. Apology list.
8–20h
Wedge
One unclaimed step. Scope a 90-day obsessive product.
20–36h
Record
The data model of that job.
36–48h
Export
Leave-path demo. Present the day, not the matrix.
- Win the checkout and ignore the spreadsheet after.
- Announce a platform before a wedge.
- Let procurement impersonate the user.
- Call hostage data a network effect.
- Be too proud to touch ugly work.
The brief names the transaction. The system lives in the work around it.
Design export, open data, and a path off the platform. Usefulness should not require captivity.
- Is this just jobs-to-be-done?
- JTBD is often a slogan. Adjacent-job studio is a shadowed Tuesday plus an export test.
- Why not start with the core transaction?
- Because incumbents already defend it. The unguarded load-bearing wall is usually ugly.
- When is lock-in ethical?
- When leaving is possible and staying is still rational. Otherwise it is occupation.
- How do I find the apology?
- Watch. People narrate it: ‘sorry, this bit is messy.’ That sentence is a spec.
- Does this apply to internal tools?
- Especially. The adjacent job inside a firm is often the real ERP.
Cited for classification and method. Not as a manual. Atlas cases are educational and defensive.