Hello, I am Maryem Khaled
A UX designer who believes
The best screen
is the one nobody notices
When someone finishes the task without stopping to work out where to click, the design has done its job. Admiration comes later, if at all.
I shorten the distance between intent and completion
I work on products people return to: dashboards, booking, checkout, long forms. My benchmark is the completion rate, not the screenshot.
What Maryem adds inside a project
The difference between a form that gets filled and one that gets abandoned is usually three small details. Those details are the work.
Flows tested before they are drawn
She maps the path on paper first and counts the steps. Every extra step is a drop-off rate, and every unnecessary field is one fewer user.
The states nobody plans for
The empty screen on first use, the list with two hundred items, the error that appears after the form is already full. These are what actually shape the impression.
Designs that can be built
She hands over components with their states defined — default, loading, disabled, error — so no developer has to invent a decision nobody agreed to.
How Maryem approaches a screen
What did the user come to this screen to do? If the answer is not one sentence, the screen is carrying two jobs and they need separating.
Steps from start to done, marking every likely drop-off and why someone would stop there.
Content order and priority before colour and type, so the screen still makes sense stripped of its styling.
Empty, loading, overflowing, failing. Each one gets drawn rather than left to judgement during the build.
She opens the implemented screen and uses it as a user, not as its designer. The gap between the two always shows.
Name the task
1What did the user come to this screen to do? If the answer is not one sentence, the screen is carrying two jobs and they need separating.
Map the path
2Steps from start to done, marking every likely drop-off and why someone would stop there.
Build the structure
3Content order and priority before colour and type, so the screen still makes sense stripped of its styling.
Cover the states
4Empty, loading, overflowing, failing. Each one gets drawn rather than left to judgement during the build.
Review the built version
5She opens the implemented screen and uses it as a user, not as its designer. The gap between the two always shows.
When the design is judged by completion rate
Maryem fits products people use repeatedly: a dashboard, a booking system, or a checkout you want more people to finish.
Let’s build something precise, useful, and ready to grow.
Want to talk to the person who'd do the work?
Tell us what you are building, where it is stuck, and what the next step needs to achieve. You will get a straight answer about scope and sequence — and it will come from whoever would actually build it.