Design system
When the needs reveal inconsistent page templates.
Structure your design systemNeeds definition: starting from the right needs, together
Before designing, you need to understand. I work with your teams to analyse your context and listen to your audiences, to turn a vague request into clear needs, prioritised and shared by everyone involved.
One-hour video call · no commitment · slot of your choice
Who is it for?
When should you call on a needs definition?
This service is useful when:
- You are launching a website, extranet or application project without a clear specification.
- Your departments have different priorities and struggle to decide.
- Your users are complaining, or usage figures are dropping.
- The specification was written by a single department.
You are…
Freelancer or SME
A clear view of what your customers expect, before investing in a website or a tool.
Large company
Priorities shared between departments, based on what your audiences experience rather than on internal preferences.
Institution
An information architecture designed for varied audiences, and clear editorial governance.
What?
Interviews, workshops and prioritisation: what the assignment covers
What the service includes
- Context analysis: review of existing documents, usage statistics, content inventory, comparison with other solutions.
- Interviews with your audiences and with the people involved internally.
- Synthesis: usage profiles, journeys, pain points ranked by priority.
- Workshops on prioritisation and card sorting, with representatives from each department.
- Formalisation: prioritised needs, user stories, success criteria, tested target site structure.
What you receive
- A summary report that the whole organisation can read.
- A prioritised needs matrix.
- A site structure tested with your users.
- Governance recommendations: who publishes what, and how.
Why?
What a needs definition changes for your projects
- Faster decisions: priorities are based on facts, shared by everyone.
- Less unnecessary development: what is built meets a real need of your audiences.
- Departments that move forward together: everyone has been heard and understands the trade-offs.
- A solid foundation for what comes next: design, design system, content, training.
In practice
How the support works
Step 1: Discovery call
Free, one hour: your context and your objectives.
Step 2: Scoping
Scope, people to involve, schedule, success indicators.
Step 3: Listening
Context analysis and interviews.
Step 4: Workshops
Shared synthesis and collective prioritisation.
Step 5: Debrief
For everyone involved, not just management.
Who takes part: the person leading the project, one contact per department, end users and, from the start, IT for technical constraints.
Going further
Documentation and training
When editorial governance is the real issue.
Train your teams
Have a project in mind? Let's talk.
In one hour, I review your context, your constraints and your audiences with you. You leave with a concrete lead for what comes next, and a short summary note.
One-hour video call · no commitment · slot of your choice
Prefer to write? Email contact@bhen.be — reply within 3 working days.
