On every SSB software product
Flat 30% discount on any software
School, hospital, hotel, restaurant, HR, lab, pharma and the rest of our software. Ask for a quote and we apply 30% on the price. Write to info@ssbconsultancy.com.
Design that starts from a moodboard produces a product people admire and avoid. The work is to watch the task: where they stop, what they ask a colleague, and which field they leave blank.
The usual brief is “make it modern”. The current screen is ugly and also confusing, and only the second problem costs money. Staff keep a paper note because the software asks for twelve fields before it asks for the one they came to enter.
We sit on one task. We remove what that task does not need. You click a prototype. If you get lost, we change the prototype, not a finished build.
Visual design follows the path. Colour and type are part of the job. They are not a substitute for being able to finish.
From open to done, including the mistake people make
You try it before engineering spends a month
What is not needed for the task is not on the screen
The screens match a flow engineering can estimate
The screen collects everything the database knows and the user needed one field.
Labels use vendor words the staff do not use.
Errors appear after submit, with no hint about what to fix.
A redesign is approved from a still image nobody tried to use.
Engineering estimates a picture, then discovers the flow was never decided.
One primary task is designed end to end before secondary tasks.
Labels use the words your staff already say.
A mistake is explained at the field.
You click the prototype with a real example. Approval means you finished the task.
The build estimate uses that flow, so the picture and the scope are the same thing.
The current screen, paper or chat. Where people stop is the brief.
The fields the task needs. The rest are later or gone.
A prototype with your example, not a slide.
Engineering can quote it. If the path is still wrong, we do not build it yet.
No. Visual design is included. The part that matters first is whether someone can finish the task. A beautiful screen that needs a phone call to complete has failed.
Yes. Bring the screen people avoid. We start there, not from a new homepage.
Only for work that is already understood. For the confused task, building in parallel recreates the confusion in code. We would rather delay that part.
The flow, the prototype you tried, and the notes engineering needs. You should be able to reject it before a developer starts.
A brochure site looks finished and still leaves orders, applications or bookings in email. Web development here means the page that does the job.
The demo phone is new. The customer’s phone is not. Mobile work starts from the action on a ordinary connection, not from a store screenshot.
The happy path works. The cancel, the duplicate and the empty field do not. QA is that list, run before customers find it.
Tell us the operation that is breaking. We will walk that screen and send a written quote.
We reply instantly
