FROM FEEDBACK TO FLOW / AN ILLUSTRATIVE WORKFLOWSkip sequence
01 / 04
Listen.
A request is the beginning of a conversation.
Select a card to read the request.
01Listen
02Understand
03Explore
04Refine
OPEN A CARD · SCROLL TO CONTINUE
This concept shows a design process, not customer testimonials. The final patching prototype is a simulation with no hardware connected. Example requests and user needs can be opened for more detail. Listen to both problems and proposed solutions, understand the user need, explore a workflow and refine the experience.
Explore the requests and needs.
01 / PRODUCT DIRECTION
Product direction.
Turn user insight into a clear development direction.
Community feedback, commercial priorities and technical realities all deserve a place in the conversation. I help teams understand the problem behind a request, weigh the wider impact and define what a useful, lovable product should deliver.
Ways I can help
Feedback and workflow reviews
Feature definition and prioritisation
Product briefs and acceptance criteria
When the feature list keeps growing, but the next step is unclear.
02 / UX & UI DESIGN
UX & UI design.
Make complex tools feel understandable.
Professional users need depth, speed and predictable behaviour. I help shape interactions that support their work, respect established habits and make new capabilities easier to discover. The workflow, the interface and the language need to make sense together.
Ways I can help
Interaction flows and interface concepts
Usability, terminology and consistency reviews
Experiences across hardware and software
When a capable product takes too much effort to learn or use.
03 / TECHNICAL ADVISORY
Technical advisory.
Connect the product to the production around it.
A fixture, console or distribution device is part of a wider system. I bring a practical production perspective to development discussions, looking at how people configure, connect, operate and troubleshoot the technology in real use.
Ways I can help
Fixture and control concept reviews
Setup, configuration and diagnostics workflows
Data distribution and system integration reviews
When you need an outside perspective grounded in show experience.
04 / WHERE IT FITSTHE PRODUCT IN ITS WIDER CONTEXT
Lighting. Control. Everything in between.
LIGHTING FIXTURES
Clear control.
Configuration, feedback and everyday operation. Helping the experience around a fixture match what it can do.
CONSOLES & CONTROL
Fluent workflows.
Tools that support both learning and experienced use, with meaningful features and dependable interactions.
INFRASTRUCTURE
Understandable systems.
Data distribution, setup and diagnostics. Making the connections and the state of a system easier to understand.
05 / WORKING TOGETHER
The right involvement for the next step.
We agree the question, scope and useful outputs before starting. A focused review can stand on its own or help define a longer collaboration.
A focused review
Bring one concept, interface or workflow and a question you want to resolve. We agree what to examine, then work through practical recommendations your team can use.
Start with
A walkthrough, screenshots or a prototype, who uses the product, and where they run into difficulty. A finished specification is not required.
Useful outputs
A prioritised set of observations, annotated examples where useful, and recommended next steps for the agreed question.
Discuss together
A walkthrough of the reasoning, trade-offs and what your team could take forward. Scope, outputs and fee are agreed before work starts.
For example: Operators struggle to find the right patching controls. A focused review could examine that workflow, identify where navigation or feedback becomes unclear, and recommend changes to explore with your team.
A development sounding board
An outside perspective when your team needs to work through a product decision.
Start with
A feature request, a workflow problem or a decision in development.
Useful outputs
Feature definitions, acceptance criteria or annotated workflow and interface feedback, as agreed.
Discuss together
The reasoning and implications with your product and development team.
An ongoing advisory role
Regular collaboration as your product develops and you learn from its users.
Start with
Your product priorities, user feedback and development context.
Useful outputs
Reviews and recommendations as the product evolves, with scope and cadence agreed together.
Discuss together
Revisit decisions as new feedback, constraints and release priorities emerge.
A product idea, a workflow to improve, or a question that needs another perspective. Send me a message, or use a few guided questions to shape your brief.