Decision memo
A plain-English read on the problem, tradeoffs, risks, and recommended path.
Consulting
Product and engineering judgment for teams that need to move.
I work with founders and operators who have enough context to know something is blocked, but need a clearer diagnosis, a sharper tradeoff, and a plan their team can execute. FAST.
Good problems to bring
- Your roadmap has too many priorities and no obvious order of attack.
- An internal tool, Rails app, or workflow is important but hard to change safely.
- Product, design, and engineering are talking past each other.
- You need a senior outside read before committing time, money, or team attention.
What you get
Execution sequence
The first useful moves, ordered by leverage, dependency, and reversibility.
Technical and product review
A practical assessment of code, workflow, UX, infrastructure, or product direction.
How it starts
The first call is a fit check, not a sales ceremony. If the problem is crisp enough, we define the shape of the working session or short engagement. If it is not a fit, I will say so directly.
Best fit: small teams, internal software, product operations, Rails or web application work, UX/UI judgment, and technical decisions where practical experience matters more than a generic framework.
How I work
-
1. Diagnose the bottleneck
We separate symptoms from the constraint: product confusion, technical drag, process friction, or unclear ownership.
-
2. Choose hard tradeoffs
We narrow options, name the cost of each path, and choose the move with the best chance of changing outcomes.
-
3. Turn it into an execution plan
You leave with a clear sequence, owners, and first actions your team can start immediately.
Proof of work
Outcome
From crowded roadmap to shipped plan
Turned competing priorities into a smaller sequence with clearer ownership, fewer active workstreams, and a path engineering could actually execute.
Operating range
Product judgment plus hands-on implementation
Useful across Rails applications, internal tools, UX/UI decisions, infrastructure, and the messy space between business requirements and working software.
Not a fit
- Work that needs a large agency team from day one.
- Projects where nobody with authority can make tradeoffs.
- Vague advisory work with no path to a decision or shipped improvement.