Design for the customer’s next decision
The first screen should answer four questions: what are we trying to achieve, where are we now, what do you need from me, and what happens next? Prioritize customer-owned actions and near-term milestones over internal project detail.
- Show a concise outcome statement and target milestone.
- Group tasks by phase and owner, with clear due dates and dependencies.
- Explain why each request matters and what a complete response looks like.
- Keep completed work visible without letting it overwhelm current actions.
Create one source of truth
Move the project plan, file requests, forms, decisions, and status updates into the portal. If the team continues making important decisions in private messages, customers learn that the portal is optional.
Use email and chat as notification channels that point back to the durable record. This preserves convenience while protecting context.
Reduce friction at every request
Customer work should be easy to understand and easy to complete. Use plain language, reasonable file constraints, saved progress for long forms, and examples for unfamiliar inputs. Test the experience as an external user with no internal context.
- Avoid exposing internal status codes, team shorthand, or irrelevant subtasks.
- Use magic links or single sign-on where security requirements allow.
- Make mobile review possible for approvals and short responses.
- Provide accessible labels, keyboard navigation, and clear error recovery.
Publish a predictable communication rhythm
Post a weekly update even when there is little change. Include progress since the last update, current health, the next milestone, decisions needed, and any risk to the target date. Predictability creates trust and reduces ad hoc status requests.