Key takeaways
- Design around a single job to be done, not a department.
- 42-field forms are a symptom, not a spec.
- Ship the smallest thing that removes a phone call.
01 — Section
Why most portals quietly die
Every portal we've rescued had the same disease: it was built as a mirror of internal processes, not as a tool for the person clicking. The result is a form with 42 fields that nobody wants to fill, and a support inbox that keeps getting the same three questions.
02 — Section
Start with one job
Pick the single interaction that generates the most inbound calls or emails, and design the portal around removing it. Ship that. Measure the drop. Then take the next one.
This sounds obvious. It is almost never how portals get scoped — which is exactly why the ones that follow this pattern feel completely different to use.
03 — Section
Progressive disclosure over exhaustive forms
Ask for what you need to move to the next step, not what the database wants eventually. Long forms should feel like a conversation, not an audit. Every field earns its place or gets deferred.
“The org chart can wait. The person clicking cannot.”
Working on this?