Department priorities are clearly linked to wider organisational goals.Operational work and project work sometimes compete without clear priority.When organisational priorities change, department commitments are adjusted.Teams are sometimes unsure which work should come first.

Responsibilities are clear inside the department and at important handovers.Some decisions wait for individual managers and can become bottlenecks.Escalation paths and decision rights are understood by the people involved.Ownership can become less clear when work crosses team or function boundaries.

Defined processes match the way work is actually done.Teams use local practices to keep important work moving.Process owners, deviations and needed changes are actively managed.Comparable work is sometimes done differently across teams.

Department project commitments and milestones are visible and monitored.Some project commitments are accepted before department capacity is fully confirmed.Dependencies between department work and wider project delivery are managed.Getting a reliable project status often needs manual follow-up.

Workload, available capacity and important skill constraints are visible.Key people are often needed by several operational or project topics at the same time.Competing demands are prioritised using defined criteria.Capacity shortages sometimes become clear only after delivery is affected.

Managers have a reliable view of important work, status, dependencies and commitments.Operational information is spread across spreadsheets, emails and different tools.Regular reporting needs a lot of manual collection and consolidation.Important decisions, responsibilities and next steps are traceable.

Relevant indicators show emerging workload, quality or delivery problems early.Some problems become clear only after another team, project or customer is affected.Escalated issues have clear owners, actions and follow-up dates.Recurring coordination meetings do not always lead to lasting resolution.

Recurring issues are reviewed beyond the immediate symptom.Improvement actions are assigned and followed up.Good improvements often stay local and are not shared with related teams.New working practices sometimes lose momentum after the start.