Product diagnosis
To turn a messy problem into a scope the team can actually decide on and prioritise.
- A read of the context and the constraints
- A map of risks, flows and opportunities
- A recommended next step
Pallus Massucci · Independent studio
I work with teams that need to define, test and ship clearer digital experiences, connecting business, technology and the people who run the product every day.
Talk about a projectWhen it makes sense
Work
Delivered projects and self-initiated redesigns, the latter labelled as proposals. Each one opens with the problem that existed, the decisions taken and what was measured.
Marketing and lead capture site, live.
The price list as the argument, not as a buried table.
The clinic's best asset was buried in a bullet point.
Two specialties, one page, no decision made.
From the briefing in a chat to finished PSDs, with two approvals of mine.
Ways of working
Scope is agreed after a short conversation about context, constraints and what needs deciding. Timelines vary with access, rituals and team availability.
To turn a messy problem into a scope the team can actually decide on and prioritise.
To test a critical journey before committing engineering to the wrong solution.
To take a validated experience into development with technical clarity and less rework.
AI, where it helps
I use AI to speed up exploration, prototypes and handoff, without skipping research, validation with people or technical limits.
See it appliedNext step
Tell me the context. I will come back with a proposed scope, format and next step.