- The outcome
- New hires are productive in their first week, not their first month.
- How we’ll know
- Time from start date to first completed task, measured before and after.
- By when
- One quarter.
- Not in scope
- Replacing the HR system. It’s fine.
Approach
Start at the end.
Outcome-based work is simple to describe and hard to fake. We agree on what should be different when we’re done, then let that decision run the project.
The outcome brief
One page. No acronyms. Signed by both of us.
Every engagement begins with a short document that says what will change, how we’ll all know it changed, and what we’re deliberately leaving alone. It is the thing we check every decision against.
If it can’t fit on a page, the outcome isn’t clear enough yet, and that is worth finding out before anyone writes code.
The four steps Listen → Frame → Build → Prove
What an engagement feels like.
-
Listen
We start with questions, not a pitch. What is slow, what is expensive, what keeps slipping? You talk and we take notes.
Expect a conversation or two with the people closest to the problem. No discovery phase that lasts a quarter.
-
Frame
Together we write a one-page outcome brief: what will be different, how we will measure it, and by when.
Plain language, no acronyms. If the brief cannot fit on a page, the outcome is not clear enough yet.
-
Build
Working software early and often, so you can see progress instead of reading about it.
Each decision is checked against the brief. Scope that does not serve the outcome is parked, in writing, for later.
-
Prove
We measure against the brief and show you the result. Then we make sure your team can run it without us.
Handover includes documentation, the working system, and the knowledge to operate it.
Fine print In large print
What “outcomes-based” means here.
It means
- A written outcome before any build begins
- Progress you can see in working software
- Honest check-ins, including when the plan should change
- A handover your team can actually run
It doesn’t mean
- Hours logged as a measure of value
- A slide deck as the final deliverable
- Technology for its own sake
- Lock-in. We build so your team can take over.
Questions
Things people ask first.
What if we do not know the outcome yet?
Most people do not, exactly. That is what the first conversations are for. You bring the problem and we help turn it into something measurable.
Is this only for large projects?
No. An outcome can be as small as “this report builds itself.” Small, well-defined outcomes are often the best place to start.
Do you work with public-sector organizations?
Yes. Our federal team is based in Arlington, Virginia, and our corporate headquarters is in Austin, Texas.
What happens after you finish?
We hand over the working system, its documentation, and the knowledge to run it. We are glad to stay on as a partner, but the goal is that you do not need us to.
Next step