Service
The ask is where the work starts. And rarely where it ends
one practice
Two ways to engage.
Four pressure points.
The problems worth solving rarely sit inside one function.
They live in the seams between them —
where engineering meets regulation, where the product meets the market,
where the decision meets the people who have to run it.
Assign that problem to one team and they solve their part.
The seam stays open.
I work across the seams.
the Shape
Form follows what we find.
What follows depends on what the work requires.
Most engagements take one of two shapes.
Diagnostic
A focused engagement to find what's driving the ask
and set the direction. It takes as long as seeing clearly takes —
usually weeks, sometimes longer when the problem is tangled.
It ends with a clear read on the problem,
what depends on it, and what your team can act on next.
Embedded
The deeper engagement: design the structure,
carry it through implementation, and leave it running without me.
I work inside the organization, across the seams,
for as long as the work requires.
Some programs take months.
The ones breaking new ground or carrying real risk take years.
The form can flex.
What the work requires stays the same.
That means access to the problem beneath the ask,
and permission to follow it
across the people, evidence,
and decisions that shape it.
Enough candor for disagreement to be useful,
and enough room for evidence to lead.
Someone accountable for what happens next,
with the authority, support, and continuity to build
the structure the work requires —
and carry it through implementation.
The deeper the work goes,
the more those conditions matter.
FOUR PLACES
The same pressure, in different forms.
Clarity
Clarity is possibility.
Unity from the boardroom to backlog.
Where it starts
The stated problem is accurate — and incomplete.
What keeps it unresolved often sits outside the frame: unclear ownership, competing assumptions, or an unnamed consequence.
A product question turns out to be an operating problem.
A brand issue turns out to be an offering mismatch.
The business keeps moving. The decision doesn't.
Each return costs more.
This is the loop that holds until the frame changes.
How I work
I find what's load-bearing and change only what can no longer carry the work.
What is straining is not necessarily broken.
Sometimes strain is evidence of growth:
the business may have outgrown a system built for a smaller ambition.
What carries forward
the logic behind the decision is documented,
so the team can carry it into what comes next.
The same decisions stop returning in different forms.
The team moves without reconstructing the logic each time.
Clarity determines what must be true.
Systems make it repeatable.
Systems
Launch with precision.
Scale with proof.
Where it starts
The next variant exposes structural gaps — the team has to reconstruct the interaction logic, rewrite the specifications, and resolve in sustaining engineering what development left unclear.
Critical decisions remain in people’s heads instead of being built into the product, its documentation, and the operating model around it.
Incoherence is what makes the next variant expensive.
Coherence is what buys durability.
How I work
I make intent and proof explicit in the product architecture: how decisions connect, how intent becomes behavior, and what evidence will show the system works.
I shape enough structure to guide development, not constrain it —
a foundation the business can build from, not an anchor that holds it in place.
What carries forward
The next product begins where the last one ended.
Each launch is more precise because the system can withstand scrutiny.
Scale becomes possible because the proof is already inside the work.
Systems carry intent into use.
Adoption reveals what people do with it.
Adoption
Use is the test.
Behavior is the proof.
Where it starts
when the day won't slow down, the moment demands something the testing never simulated.
People skip steps,
follow different cues,
invent workarounds.
The organization sees that evidence in fragments —
support, analytics, research, sales, and direct use.
Adoption you can't see is value you can't reliably repeat.
How I work
The gap between what people were meant to do and what they do is the symptom. What produced that symptom is where the work begins.
The scope follows the evidence —
sometimes a single interaction, sometimes the operating model.
What carries forward
Behavior becomes evidence the team can draw on to reduce avoidable support, shape the next release, and make future adoption easier to earn.
Adoption turns behavior into evidence.
Narrative gives it meaning in the market.
Narrative
Say what you can prove.
Prove what you say.
Where it starts
and reliably deliver, the market feels the gap before it can name it.
The problem sits deeper than language.
Claim, proof, and delivery pull in different directions. The buyer is left to reconcile what the company says with what the evidence supports, and what the experience confirms.
Commercially, the drift has a shape:
Buyers slow down and ask for more proof.
Price becomes the place uncertainty gets negotiated.
Pilots start carrying production work the proposition was meant to do.
Inside the business, the same signals get misread.
A pricing problem gets treated as a product problem. A proof problem gets treated as a messaging problem.
How I work
Then I baseline what the product does against what the marketing says, what the specs state, and what the team believes, then test all of it against how the product is experienced.
That baseline helps distinguish a messaging problem from a proof problem, and a pricing signal from a product problem. What survives is what the story can grow from.
When claim, proof, and delivery converge, the gap buyers feel but can't name begins to close. As uncertainty falls, price has less to negotiate.
Value stands on its merits.
What carries forward
The story evolves as new offers, new evidence, and new market signals arrive — without rebuilding from scratch.
What comes back from the market tests whether the claim holds in practice.
Sometimes it sharpens the story.
Sometimes it reopens the first question: what are we solving?
Clarity names what is true.
Systems make it repeatable.
Adoption shows how it performs.
Narrative gives it meaning the market can act on.
Leadership
Possibility is the orientation.
In most organizations, the knowledge already exists. It’s distributed.
Engineering
knows what is possible.
Operations
knows what can be sustained.
Regulatory
knows what can be defended.
Sales
knows what buyers resist.
Support
knows where people struggle.
Each holds a different part of the same decision.
The work may enter through one function.
The mandate has to reach as far as the problem does.
I listen closely to what is being said and watch what happens around it.
I use curiosity to find where there is room to go further.
I bring what each function knows into the same choice, while there is still room to shape it.
I make the tradeoffs visible — cost against the trust it buys, speed against risk — and keep the differences useful long enough to see where they lead.
I make the reasoning visible and the ownership clear, so people can challenge it, strengthen it, and carry it forward.
The next decision starts from a stronger place.
Their words
With a remarkable ability to create a singular vision through a forest of options...
Jen manages to create signal out of noise.
When pressure rises,
Systems matter.
Make it clear.
Make it work.
Make it last.