In this post
Repeatable structures go further than individual actions
Digital structures connect a task with a reliable workflow, a responsible role, a usable information basis, and a checkpoint. They make good results repeatable and problems correctable.
Actionism occurs when companies respond to every new signal with another individual measure. This increases activity, but not necessarily the ability to learn or impact.
Starting point
Following a phase of accelerated digital implementation, many companies faced a new task at the end of 2021. Numerous short-term measures had to be transitioned into reliable operations.
Newsletters were set up, platforms activated, virtual formats established, and new tools introduced. Some solutions had proven themselves. Others persisted simply because no one had time for a fundamental evaluation. At the same time, new requests and further projects emerged.
The visible activity could convey the impression that the company was developing continuously. In reality, a structure connecting decisions, implementation, and evaluation was often lacking. Every action started anew with coordination, data searching, approval, and clarification of responsibilities.
What lies behind the problem
Urgency crowds out repeatability
Under time pressure, teams focus on the immediate result. This makes sense in an acute situation. It becomes problematic when the provisional workflow becomes permanent.
Important questions remain unanswered:
- Who has the necessary access?
- Where are approved statements and materials located?
- Who reviews technical and legal requirements?
- How are requests passed on?
- What data is collected and evaluated?
- When is it decided whether the measure will be continued?
Without these answers, the next execution will again depend on individuals and improvised coordination.
Activity becomes more easily visible than structure
A new campaign, a post, or a tool can be showcased. Working on roles, templates, data rules, and review routines is less visible. It operates internally and is therefore often deprioritized.
However, it is precisely this invisible layer that determines whether a company becomes faster or slower. A clear structure reduces inquiries, duplicate entries, errors, and recurring fundamental discussions.
Structure is confused with bureaucracy
Resistance to processes is understandable when processes only generate additional documentation and approval loops. However, a digital structure is not automatically a comprehensive set of rules.
The minimum viable structure answers five questions:
- What is the purpose of the task?
- Who bears responsibility?
- What information and systems are required?
- How does the handover or approval work?
- How can you tell if an adjustment is necessary?
Everything else must be justified by risk, frequency, or complexity.
Strategic Classification
Quality and service management do not treat processes as an end in themselves. The process approach is intended to make interactions understandable, clarify responsibilities, and enable continuous improvement. The GOV.UK Service Manual similarly describes the ongoing operation of a digital service as a sustainable task involving planning, budget, and regular improvement.
For companies, this results in a central distinction:
- A Single action delivers a one-time result.
- A digital structure creates the ability to generate comparable results repeatedly, in a controlled manner, and with the capacity to learn.
Both have their place. Not every one-time task requires a permanent process. However, recurring or business-critical tasks should not be reinvented every time they are performed.
Structure does not reduce every deviation
A robust structure does not rigidly prescribe every single step. It defines the standard case, makes exceptions visible, and regulates who decides on a deviation.
Especially in digital work, change is normal. Content, platforms, technology, and requirements evolve. Rigid instructions become obsolete. A good structure remains focused on purpose and responsibility and can adapt its workflow.
Learning loops are part of the process
Many processes end with publication or technical completion. This misses the most important part: feedback.
A learning loop connects:
- expected impact
- observed result
- technical interpretation
- Decision
- Adaptation of the process or the measure
Without this step, a company repeats not only its successes, but also its mistakes.
Perspective from practice
Digital structures are often planned on too large a scale. Teams try to document all special cases and create comprehensive manuals. The project stalls before the first reliable workflow has been established.
A step-by-step approach is more practical:
- start with a frequent or high-risk process
- observe the actual path
- remove unnecessary steps
- Clarify responsibility and handovers
- create brief, usable documentation
- add a measurement or inspection step
- adjust the workflow after several iterations
A good process is not measured by the length of its documentation. It is measured by whether different participants understand the same purpose, handovers function smoothly, and problems do not have to be analyzed from scratch every time.
Three warning signs of missing structure
Dependency on individuals: Only one person knows how content is published, data is analyzed, or campaigns are set up.
Recurring fundamental questions: With every new measure, target group, approval, data access, and responsibility are discussed again.
No conscious termination: Measures continue to run even though benefits, maintenance, and responsibility are unclear.
These signals do not point to a lack of effort. They point to a lack of systemic capability.
From action to digital structure
Framework of action
1. Select recurring friction
Do not start with a comprehensive process program. Choose a task that occurs frequently, connects multiple roles, or regularly generates errors. Examples include publishing expert content, processing digital inquiries, or evaluating a campaign.
2. Make the actual workflow visible
Document what actually happens today. Avoid an idealized description. Note waiting times, queries, media disruptions, missing information, and decisions without a clear role.
3. Clarify responsibilities and handovers
Determine who owns the workflow, who conducts the business review, who implements it technically, and who decides in exceptional cases. Define what information makes a handover complete.
4. Define minimum standard
Create a brief checklist, template, or process map. The standard must be concise enough to be used in everyday work. Add only requirements that demonstrably improve quality, safety, or speed.
5. Review result and process together
Do not evaluate only the visible outcome. Also examine effort, delays, sources of error, and queries. Adjust the standard if the initial situation changes or better ways become apparent.
What companies should not do
Companies should not turn every digital task into an extensive approval process. This creates bureaucracy and shifts responsibility to committees. Nor should a standard remain unchanged just because it was documented once.
Another risk is automating an unclear workflow. Automation increases speed, but it neither clarifies purpose nor exception handling. The contribution “Automation does not save unresolved processes” deepens this connection.
Consequences for companies
Digital maturity does not arise from the number of measures, but from the ability to reliably repeat relevant tasks and learn from results. For this, companies do not need maximally detailed processes. They need a few clear structures at the decisive transition points.
These structures form the foundation for a reliable roadmap. Only when responsibilities, prerequisites, and workflows are visible can initiatives be realistically prioritized and connected. This addresses "What a robust digital roadmap must achieve".
The difference between activity and strategy is found in "More digital measures do not create a digital strategy". The permanent systemic perspective provides "Digital presence is not a finished project". The general overview is available in Subject Areas Digital Strategy.
Subject-matter connection
combine strategy and operations in a shared structure
The SDC Partnership supports companies not only in formulating digital priorities, but also in translating them into clear roles, processes, systems, and learning loops. It steps in where individual measures exist, but their connection and permanent control are missing.
Classify SDC Partnership as a structural and governance framework
Sources and technical foundations (5)
- GOV.UK Service Manual, „Managing and improving your service through its lifecycle“. Open source
- GOV.UK Service Manual, „Iterate and improve frequently“. Open source
- ISO, „Quality management principles“. Open source
- ISO, „Quality management: The path to continual improvement“. Open source
- Digital.gov, Web Analytics Playbook, „Do it continuously“. Open source
