How I work / Discover & Plan
Discover & Plan
Start with the work.
Then choose the technology.
A useful project begins with a clear problem. I work with you to understand the process, identify the people it affects, and decide what is worth changing first.
Bring a real example
A recurring task, a messy handoff, or a question your team answers every day is enough to start the conversation.
What this looks like in practice.
Walk through the process
Follow the work from the first request to the final result. Identify where information lives, who makes decisions, and where people lose time or confidence.
Test the assumptions
Review the systems, access, data quality, and dependencies involved. A simpler process or an existing product may solve the problem without a custom build.
Define a useful first release
Agree on what belongs in scope, what success looks like, and what can wait. Surface uncertainty early instead of turning it into an unexpected commitment later.
Leave with a decision you can act on.
Discovery should make the next step clearer. Depending on the agreed scope, the output may include a workflow map, a comparison of options, a proposed architecture, and a focused implementation plan. It should also identify unresolved questions and who needs to answer them.
Points to agree together
- The business task and intended users
- The information, tools, and access required
- The proposed scope and important exclusions
- How the first version will be evaluated
A few useful answers.
Do I need a specification?
No. Bring examples of the work and the friction you experience. We can define the requirements together.
Does discovery commit me to a build?
No. Discovery and implementation can be scoped separately. The right result may be a smaller change, an existing tool, or a decision to wait.
Find your next step.
Explore AI Strategy & Architecture
Have a process or project in mind? Tell me what you want to improve, and we can discuss a sensible starting point.