[User Story] Focused workflow mode guides users through the current job with reduced interface clutter #3

Open
opened 2026-07-14 20:08:44 +02:00 by zemion · 0 comments
Owner

Problem / User Need

Workflow should help users navigate the system for a specific process. In workflow mode, GovOPlaN could reduce the visible interface to what is needed for the current step, track progress, and keep users oriented without permanently hiding broader system capabilities.

Acceptance Criteria

  • Define a workflow-guided UI mode that can frame the current step and progress of a workflow instance.
  • The mode can reduce visible navigation clutter, including side rail/subnav, to the relevant actions for the current step.
  • Users can intentionally leave the focused mode and return later.
  • The system shows open workflow tasks/reminders and a clear path back to the active workflow.
  • Step-specific module handoffs use consistent buttons, placement, behavior, and visual language.
  • The design principle is documented: reduce interface clutter for the current job while preserving discoverability and escape hatches.

Notes / Decisions

This is intentionally rough and should become a design principle plus a workflow/core UI contract before implementation. It links strongly to the new user-story issues around guided monthly data workflows and permit-to-payment.

## Problem / User Need Workflow should help users navigate the system for a specific process. In workflow mode, GovOPlaN could reduce the visible interface to what is needed for the current step, track progress, and keep users oriented without permanently hiding broader system capabilities. ## Acceptance Criteria - Define a workflow-guided UI mode that can frame the current step and progress of a workflow instance. - The mode can reduce visible navigation clutter, including side rail/subnav, to the relevant actions for the current step. - Users can intentionally leave the focused mode and return later. - The system shows open workflow tasks/reminders and a clear path back to the active workflow. - Step-specific module handoffs use consistent buttons, placement, behavior, and visual language. - The design principle is documented: reduce interface clutter for the current job while preserving discoverability and escape hatches. ## Notes / Decisions This is intentionally rough and should become a design principle plus a workflow/core UI contract before implementation. It links strongly to the new user-story issues around guided monthly data workflows and permit-to-payment.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-workflow#3
No description provided.