Skip to main content

Time (step by step)

Introduction​

This section focuses on processes and best practice to follow to make a success of implementing digital standards.

Introduction to Time

Naturally, thoughts turn to project management techniques and similar processes, when we talk about the steps to follow. These digital standards do NOT have the intent to promote a certain project methodology etc. Instead the focus on the order of activities to be successful in reaching the required standards e.g. you cannot put a website in production without securing the domain first.

Ideation​

People have ideas all the time!

The above is a blunt statement, but consider if someone told you to manage ideas. Then you start to consider what 'Ideation' means. It is a term often with a hint of consultant jargon about it, if you look it up online, but generally it follows a natural progression

  • Problem Identification: Clearly defining the problem or opportunity that needs to be addressed.
  • Idea Generation: Using techniques like brainstorming, mind mapping, and SCAMPER to come up with a variety of ideas.
  • Idea Evaluation: Assessing the feasibility and potential impact of the generated ideas.
  • Feedback and Iteration: Refining ideas based on feedback from potential users, advisors, and mentors.
  • Implementation: Turning the refined ideas into actionable plans or solutions.

If we view these steps from the perspective of achieving high digital standards, it begins to look more like

  • is this worth addressing? Our time is finite.
  • has this problem already been addresses? If there is a good answer or good way of doing it, hopefully it finds its way into these standards. As the coders would say DRY -Don't Repeat Yourself
  • How can we evaluate if it will work? In the digital world, often the preparation to find the answer takes longer than finding the answer.
  • How can we iterate to refine and learn? How do we do things more effectively? How can we speed up the local loop? How can we reach conclusions and answers?
  • How much effort will it take to implement? Consider the effort, skills, timelines etc.

It all points towards

  • ideas need to be validated
  • worthwhile ideas need to be incubated
  • strong ideas need to be able to grow into solutions

There is a sequence to this, and following Digital Standards from the earliest opportunity should reduce the effort and allow progression into a formal project to realise the idea, and then on to deliver the answer to the initial problem and hopefully a lot more.

Project Management​

For those looking for project methodologies, we recommend reviewing the "GRP-IT PMO Wiki" on Sharepoint. There you can find out about topics like

  • how project management is done in Essity
  • the tollgate approach
    • TG1 - Initiation
    • TG2 - Preparation
    • TG3 - Finalize requirements
    • TG4 - Project Execution
    • TG5 - Transform to Run mode
    • Termination (of the project)
  • project management for risks, resources, communication etc.
  • financial management of OPEX, CAPEX, benefit calculations etc.

Our Digitial Standards instead will focus on

  • proven ways of working
  • creating artifacts (like diagrams, like code, like configurations, like architecture) which will evolve and provide use
  • demonstrating value as of several threads in the solution, like project management, like security, like financials, like legislation, like skills ... all interdependent, all wound together.

Operations​

The consideration of Digital Standards continues throughout the life of the solution, from minor enhancements to major upgrades.

In daily operations, doing observability effectively is vitally importnant

Supporting evolving business services is fundamental

Major step change through migration, acquisition is to be expected

Retirement​

Eventually retirement will come, and even there, there are standards to help guide how to get the best from such periods.

In summary​

we are considering how to provide the best guidance and standards throughout the entire lifecycle of a solution

  • ideation
  • proof of concept
  • path to production
  • opeartions and support
  • retirement

The sections describe the digital standards in each phase of a solution.

Ideation​

How to apply digital standards from the outset, and how adhering to them helps to validate if the idea is worthwhile

Proof of Concept​

How we can follow standard approachs to effectively turn an idea into a concept. Then gain the benefits from doing the concept in a manner compatible with any subsequent evolution into a project.

Path to Production​

With a valid concept, describe the techniques and ways of working to meet the needs of various project management methodologies and ensure useful, high-quality deliverables and outcomes to be ready for operations.

Operations and Support​

Continuning the benefits of applying standard approaches once in operations to help maintain and evolve our solutions, onboard new team members, demonstrate business value etc. in a consistent way.

Retirement​

Eventually even the best solutions lose their value and head of retirement. Here we describe how standards continue to provide guidance around the correct ways to capture residual value, archive data correctly, decommission resources to avoid incremental expenditure and risk exposure etc.