Engagement 03 · Senior capacity, for a while
Embedded Senior Product Design
Senior design ownership of one initiative, inside your team rather than beside it, for a defined stretch.
- The situation
- An initiative that needs a senior owner now
- The team
- Yours. Your standups, your tools, your cadence
- You leave with
- The initiative shipped, or handed over cleanly
The situation
There is an initiative that matters, and it needs someone senior to own the design of it end to end. Hiring for it takes months you do not have, and it may not be a permanent role once this is done.
An embedded engagement in practice: Turning disconnected grant tools into one trusted platform.
How it works, step by step
Four steps, in order, each one something you can check off.
-
Agree the initiative and what done means
One initiative, with a written definition of what finished looks like. Embedded work that starts without this becomes general capacity, and general capacity is how a defined stretch turns into an open-ended one.
-
Join the rhythm you already have
Your standups, your tools, your review cadence. I am not running a parallel process next to your team, and the point of embedding is that there is no handover meeting between me and the people building it.
-
Own the design work end to end
Research through to the built thing, including the unglamorous middle: the states, the edge cases, the pull-request comments. Ownership means the parts nobody volunteers for, not just the parts that present well.
From the USDA engagement: the portal, owned end to end. -
Leave it maintainable
Documented decisions, patterns your team can extend, and a deliberate handover. The measure of this engagement is what happens in the three months after it ends.
What you leave with
- The initiative shipped or handed over
- Decisions documented where your team looks
- Patterns your team can extend without me
- A deliberate handover, not a last day
Working with one person
You talk to the person doing the work
No account layer, no juniors briefed second-hand, no rewriting of what you said before it reaches the designer. You explain the problem once, to the person who solves it.
The attention is undivided and it is finite
A one-person practice runs few engagements at once. That is the point: yours gets the whole of the attention. It is also the constraint, so start the conversation earlier than you need to.
Where this is not the right fit
You need capacity spread across many small tickets, or someone to manage a design team. This is one person owning one hard thing.
Shape, scope, and cost
Scoped to the problem in front of it, so length and price come out of a first conversation rather than a menu. That conversation is free and short. If the problem is still taking shape, we start with a smaller piece that produces clarity.
Is this the one?
Tell me what is happening with your product. If a different engagement fits better, or none of them do, I will say so.
Start a conversation