WORK WITH EDISON / START WITH THE WORK
Start with how the work gets done today.
If a process relies on repeated manual fixes, teams disagree about what needs to change, or an AI idea has no clear role in the day-to-day workflow, send me one concrete situation. The first question is whether the problem is worth solving. The solution comes later.
Three situations where I can help
01The problem is still unclear
You know something is wrong, but frontline staff, business owners, and engineers describe it differently. I start by mapping the current workflow, the desired outcome, the cost of the problem, and the constraints.
First output: a problem map and a short list of what to verify first02There is a direction, but the project is stuck
A plan exists, but key rules are still open, teams are waiting on one another, or the proposed change is too hard to adopt. I can help move one clearly bounded project forward.
First output: named owners, open decisions, and a clear scope for the first version03The team wants to build this capability
For ongoing advisory or an internal workshop, we can use your own operating context to practice problem discovery, stakeholder interviews, and the core practices of forward-deployed engineering (FDE).
First output: context interviews and a tailored workshop outline Your first message only needs four things
- 01
Operating context: the company, workflow, and people involved.
- 02
Current method: how the work gets done today and which tools are involved.
- 03
Point of friction: where the work slows down, creates errors, or has no clear owner.
- 04
People involved: who is affected, who must agree, and who knows the rules.
How I start
I do not start with a large build while product facts, data, and decision owners are still unclear. I also do not treat traffic, indexed pages, or inquiry counts as proof of orders or operational results. A small initial review is usually enough to decide whether deeper work is justified.