Digital Experience & Product Consultant · PMP®
I turn complex business needs into clear digital products.
Product structures, user journeys, information architecture and implementation-ready interfaces — for consulting groups, learning platforms, marketplaces and corporate teams. Working since 2013.
Selected work
Four engagements that explain the rest.
What the situation was, what I was responsible for, and what I actually built.
Client names are withheld.
What I do
Four services. Usually one engagement.
Defining the product, designing the experience, building the thing and explaining it to a board are normally four people. Here they are one, which is why nothing is lost between them.
Digital product & UX
From an idea nobody can scope to a design a team can build.
- Product discovery and problem definition
- MVP scope and feature prioritisation
- User research, personas and journeys
- Information architecture and user flows
- Wireframes, prototypes, design systems
Digital experience & web
Websites and platforms run end to end, not handed over half-finished.
- Content structure and landing pages
- UI design and responsive front-end build
- WordPress platforms you can run yourselves
- Hosting, domains, DNS and technical setup
- Analytics, behavioural tracking, improvement
Digital delivery
For teams with a digital project, several vendors and nobody making the pieces meet.
- Requirements analysis and scoping
- Design-to-development handoff
- Stakeholder and team coordination
- Quality assurance before launch
- PMP® practice, applied at project size
Proposals & business materials
The documents an organisation is judged on before anyone meets it.
- Technical proposals and corporate reports
- Presentations and board material
- Information visualisation
- Newsletters and campaign assets
- Arabic and English, built together
How an engagement runs
Sectors
Different industries. The same problem underneath.
A cybersecurity consultancy, a data-science course catalogue and a space-booking marketplace look like different jobs. They are not. Each one is a business that knows what it does and cannot yet show it clearly. Deciding what comes first is the work; the design is what makes the decision visible.
Engineering degree in computer science, 2012, specialising in web technologies — design and development taught side by side. Which is why product thinking, interface design and implementation do not need three people here, and why nothing is lost between them.
Read the full story
About
Thirteen years between the business problem and the working product.
I started in web development and graphic design, moved into UX, and now work mostly on product: defining what should exist, structuring it, designing it, and staying involved while it gets built.
Most of that has been for organisations in Saudi Arabia and France, remotely, across consulting, professional learning, entrepreneurship programmes, real estate and marketplaces. PMP® certified — useful less as a title than as a habit: scope written down, decisions traceable, dates that survive contact with reality.
Latest note
I lost front-end work to AI. Then I rebuilt my practice around product.
What clients pay for turned out not to be the drawing or the code. It is deciding what should exist, and being accountable for the decision.
Start a project
Tell me what is unclear. I will tell you what I would do about it.
A short brief is enough to start. I reply within two working days.
Direct
What happens next
- I read the brief and reply within two working days
- A 30-minute call to understand the situation
- A written proposal with scope and a fixed price