Mobile design is reprioritization, not reduction

Moving a web product to mobile is not a matter of removing content until it fits. The smaller screen may still show the wrong things first.

Begin with the role, not the layout

Start with who is using the product. An Admin may scan status and find exceptions. An Assignee may need to complete one task. The same compressed overview will not serve both.

Ask one question first: “What does this person need to do now?” Put that action first. Keep the same roles and data underneath.

Focus and context can coexist

Less content on screen does not mean fewer capabilities. The main view can focus on the current task. A second view can show the full workflow.

Context also matters. Someone checking progress between meetings needs a different entry point from someone working in the field.

Consistency is not sameness

Use the same names, roles, states, and outcomes across web and mobile. The layout does not need to match.

Consistency means that users recognize the same system. It does not mean showing the same page at a smaller size.

Good mobile design changes the order, not the meaning.