Best Practices: Application Examples for Using the Hierarchy Module
As mentioned at the beginning, various roles in the company can benefit from the features of hierarchies. Let’s take a closer look at the different positions, the projects, and initiatives they are involved in, and the added value Clarity offers them!
Example 1: Strategy Manager Sibel and Mapping Corporate Strategy
As the strategy manager, Sibel is responsible for developing and overseeing her company’s strategy to support growth objectives, strengthen the core business, and develop and maintain competitive advantages. To this end, the organization follows the OKR management approach.
Both the corporate objectives and the strategy are assigned in a top-down manner to the company’s various areas, departments, and teams, and they are broken down into thematically appropriate sub-strategies with medium-term objectives and associated key results.
The hierarchy module in Clarity allows me to easily get an overview of the corporate strategy and how it is implemented in the individual sub-areas. On the one hand, I can obtain a quick overview of how the strategy is being implemented by individual areas and which projects, initiatives, or measures are contributing to it. In addition, we record the percentage achievement of the key results on each card as well as information on whether they are “on track” or require support. But I am not the only one who benefits from the hierarchical representation. Individual users can see at any time how their activities contribute to the global strategy, which is a motivating factor for many.
Sibel
Strategy Manager
Example 2: Product Line Manager Peter and Release Planning
As a product line manager, Peter manages a portfolio consisting of multiple company products, and he is responsible for creating, tracking, and monitoring all products within existing product lines. Especially when it comes to new development and release planning, there are many different projects and subprojects that contribute to the overall result. The ability to obtain a clear overview of the current status of the ongoing launch processes is worth its weight in gold. The hierarchical representation in Clarity can also be used profitably for this purpose.
I like to use the hierarchy module to quickly get a total overview of the release process of new products. In my role, I usually look at the ongoing process from a higher-level perspective. The hierarchical representation gives me a good understanding of the necessary subprojects and their dependencies. I can quickly see when a subproject is scheduled to be completed, and I always have an eye on the planned and actual costs of the various development stages. This feature allows me to obtain further information at an early stage and to derive necessary measures if the time or cost plan for the product release is at risk. If I ever need other key figures in addition to the planned and actual costs, I can also display these quickly and easily in the cards for the individual projects.
Peter
Product Line Manager
Example 3: IT Manager Irina and Business Capability Mapping
Every organization uses a variety of software and technologies that serve different purposes. But how can you get a bird’s eye view of which tool is used in which area or on which team, whether the respective system is actually being used, and are users finding added value in the features? Keeping an eye on the current status surrounding these issues offers considerable potential for savings by trimming unnecessary costs. Hierarchies can also help to increase the transparency of this initiative. What could this look like?
In her role as IT manager, Irina also assumes responsibility for the systems at the company. She is involved in the selection and administration of these systems, and she regularly evaluates whether they are all relevant and add value.
I created a view in Clarity’s hierarchy module that breaks down the various tools in house by role. This makes it possible, for example, to determine whether there are several systems that serve the same purpose and are therefore potentially redundant. We use the individual software cards to record a risk, technology, and value score as well as information about whether the tool is an on-premises or SaaS solution. Using these defined parameters, we can evaluate at regular intervals whether we are optimally positioned in terms of technology, whether upgrades or new solutions are necessary, or whether a software package is no longer relevant for us.
Irina
IT Manager
These three examples are intended to give you an overview and provide you with inspiration about the sheer variety of areas where the hierarchy module can be used. In almost every business area there are roles that can gain added value from the hierarchical representation of their use cases – All they need to do is to identify the possible applications.