HOW WE WORK

A method, and three ways out of it.

The assessment is the same every time — same ten dimensions, same three stages, same document at the end. What happens afterwards is not the same every time, and it is your decision rather than ours.

01 BEFORE WE START

The readiness call is a qualification, in both directions.

Thirty minutes, video, no deck. We are deciding three things, and so are you.

Is there something to assess?

A working prototype with a real user or a real signal. If there is nothing running, an assessment has nothing to look at and we will say so on the call rather than after you have paid for one.

Is the assessment the useful thing?

Sometimes the honest answer is that you already know what is wrong and need someone to fix it, or that the product needs three more months of validation before production is a question at all.

Can we be useful to you specifically?

Regulated and safety-critical products get qualified carefully. If we are the wrong firm for the job, being told that in week zero is worth more to you than being told in week two.

No repository access is requested before or during this call. If the answer turns out to be “not yet”, we never asked for it.

02 THE ASSESSMENT

Context and access, independent work, then a workshop.

One to two weeks. Half a day of your time at the start, ninety minutes at the end, and nothing in between — that middle stretch is the part you are paying us so that you do not have to think about.

01 CONTEXT & ACCESSDAY 1–2

02 INDEPENDENT ASSESSMENTDAY 2–8

03 DECISION WORKSHOPDAY 8–10

The full method, the ten dimensions and the exclusions are on the assessment page　→

03 HOW WE MAKE CALLS

Three rules, and a short list of things we will not do.

Judgment is the product. These are the rules that keep it honest when the easy thing would be to recommend more work.

KEEP WHAT WORKS

A prototype with real users has been validated in the only way that counts. The default is that it stays, and we have to argue our way to replacing something rather than the other way round.

RANK BY CONSEQUENCE, NOT TASTE

Every finding carries a cost of doing nothing and a cost of fixing it. Where the first is smaller than the second, the recommendation is to leave it alone, and that recommendation goes in the document with the same weight as the others.

WRITE IT FOR SOMEONE ELSE

The document assumes its reader has never spoken to us. If it only makes sense with us in the room, it is not finished — and it is not something you could put out to another provider, which is the test that matters.

04 AFTER THE ASSESSMENT

What happens after the assessment is your decision.

You own the document, so the next decision is yours. All three paths end in the same place.

WITH YOUR OWN TEAM

This is the default, and the document is written for it.

HandoverOne session walking your engineers through the roadmap and the reasoning. No slides, and they are expected to disagree.
Review at the risk pointsYou come back to us at the two or three tranches that carry the most risk, or you do not. Either is fine and neither is a subscription.
You shipThe engagement ends when the document has been used. That is what a finished piece of consulting looks like.

WITH UNCOOL INC.

A Production Engineering Partnership, and it starts small on purpose.

A defined implementation sprintScoped against the roadmap’s first tranche, with a fixed end date. Not a retainer, and not open-ended.
Review and adjustA roadmap written before the work started is a hypothesis. We revise it in the open when the code disagrees with it.
It stops when it stops earningWe will tell you when the most useful thing we could be doing is nothing. That is easier to say when it was never a retainer.

WITH SOMEONE ELSE

The document is vendor-neutral, and that is deliberate.

You put the spec outThe roadmap doubles as a specification. Providers are answering the same question, which is the only way to compare them.
You compare answersAnyone who reads it and proposes a rewrite has told you something useful about themselves.
You chooseWe do not need to be involved and there is no referral arrangement anywhere in this.

PRODUCTION

A system other people can depend on. There is no right of first refusal in any of the three, and no clause that makes the third one awkward.

05 DAY TO DAY

Written over spoken, asynchronous over scheduled.

We are in Japan and work with teams in Europe and the United States. Overlap is arranged rather than assumed.

ONE PERSON YOU TALK TO

You are not handed to an account manager and then to a delivery team. The person who assessed your product is the person who wrote the document and the person who answers your email about it.

NO STANDUPS

A daily meeting to report that yesterday went as expected is a tax on both of us. You get written progress when there is progress, and a direct message when something needs a decision.

DECISIONS IN WRITING

If a decision was made on a call, it is written down afterwards and sent to you. Six months later the written version is the only version that still exists.

Japanese and English, in writing and on calls. Documents use the language of the people executing them.

06 START HERE

Start with a call, not a contract.

Seven questions, about three minutes, then a scheduling link. If there is a fit you will get one within two working days; if there is not, you will get a short note saying why.

Book a readiness call See what we assess

PAID　·　1–2 WEEKS　·　YOU OWN THE OUTPUT　·　VENDOR-NEUTRAL