Collaboration starts with a decision the team cannot make from inside its own vocabulary. My part is to find the missing reader context, write down the trade-off and turn it into a product change the team can review.
When I am useful
The interface only makes sense to the team. I trace the terms, assumptions and missing instructions that a new user meets in one important flow.
Learning material has lost its route. I help turn a collection of lessons, recordings or source documents into a sequence with a clear reader task and editorial rules.
A concept needs evidence before a larger build. I can shape interview prompts, a bounded prototype or a copy-first test, then document what the exercise did and did not establish.
How the work moves
We begin with the current product, available research and the decision in front of the team. I return a short diagnosis and propose a bounded piece of work. Drafts appear early, with comments explaining the choice and the evidence behind it. The handoff records open questions as well as recommendations.
Working boundary
I can work directly with designers and engineers because I understand implementation constraints. I am engaged as a product editor, not as a fractional CTO or a substitute security team. Any prototype is scoped separately and exists to answer a named product question.
Typical collaborators
- Independent schools and teachers going online
- NGOs with educational programmes that need digitising
- Product teams working on housing, language access or civic services
- Researchers and editorial teams turning complex material into a public interface
Get in touch
Describe the audience, the troublesome flow and the decision you need to make. I will tell you whether the work fits and what information is still missing before it can be scoped.