From top to bottom—or the other way around?
Our new blog post series on hybrid project management, this time covering: top-down and bottom-up strategies, Big Bang ...
As a project manager, you’re familiar with this: When you’re planning the rollout for the shift to hybrid project management, it’s nothing more than… another project! Admittedly, it’s a rather challenging one, since there are many stakeholders and the conditions are difficult. That makes it all the more important to think through and plan your rollout from the very beginning. We’ll show you how—in Part 2 of our rollout series.

It’s kind of ironic: You want to ( finally) bring a well-functioning, modern PM system into your organization with hybrid project management —but to make that happen, you have to get the rollout off the ground using the resources your PM team still has available. In our last blog post on the Can Do rollout, we already explained how Can Do supports its own implementation from a software engineering perspective. Now let’s take a closer look at what you can do—from the perspective of sound project planning —to ensure a smooth rollout of your new project management software…
Pressure from above? Momentum from below?
Top-down and bottom-up are two different management approaches found in a wide variety of organizational areas and for diverse projects—including in rollout management.
In the top-down approach, management formulates an abstract plan—the top level sets the direction and passes the tasks down through the hierarchy. In this process, an abstract goal set by corporate leadership is transformed into concrete steps in day-to-day business operations. Example: The goal of “greater efficiency and success” proclaimed by management translates into measures in specific areas, such as the implementation of new project management software or the combination of agile teams and traditional project management methods. It is in the nature of things and in line with expectations that this principle is more commonly found in traditional corporate structures and is practiced by management levels that share this same understanding of authority.
With this principle, the process works exactly the opposite way: concrete measures at the lower organizational levels, as they permeate the hierarchies upward, coalesce into an increasingly comprehensive overarching vision. The example of bottom-up also runs counter to that of top-down: An agile team figures out how to remain agile while still making project management processes more manageable. This establishes the concept of hybrid project management within project management or the PMO—that is, the combination of traditional methods and agile projects using Jira®. This gives rise to a paradigm shift throughout the entire company, which ultimately leads to greater success and efficiency. Management does not exert pressure here, but rather motivates and channels employee engagement in ways that serve the company’s development.
In companies that (in the future) rely on hybrid project management and agile, self-managing teams, it’s safe to assume that the initiative for a rollout originated from the bottom up.
Depending on the industry and business activities, there are companies today where it’s fair to say: All employees are also users. The impact of a rollout can be correspondingly significant—and you should be clear on this before rolling out your new project management software: Should all users work with the new tool at the same time, or just a portion of them?
It’s the IT department’s nightmare and management’s dream: On Friday, everyone in the company is still working with the old software—and by Monday, they’re using the new one. In between lies a hellish weekend for IT, and afterward comes the realization: It didn’t quite work out. Because even if everything was planned down to the last detail and the technology and software cooperate, people are the limiting factor in the rollout. The result: After a Big Bang, the help desk is usually swamped. And in the worst-case scenario, the IT team spends the following weekend rolling back the changes. A “Big Bang” requires extensive planning and preparation, excellent risk management, and an IT team capable of enduring the strain. But when it works, the rollout is literally done in one fell swoop. By the way, Can Do is an example of software that can ensure even an accelerated rollout runs smoothly: because Can Do comes with its own migrator for integrating existing software tools and thus integrates itself into your software landscape largely automatically.
A rollout that follows the iterative principle, on the other hand, is a much calmer process. Instead of introducing the entire software package at once, smaller components and tools are introduced first. These are then used in parallel with the existing system and can be thoroughly tested. The advantage here is that users are gradually introduced to the new features and can get used to new workflows. Furthermore, errors usually don’t have as far-reaching an impact as they do in a “big bang” rollout. The downside: It takes time. And if, for example, resistance arises among users during the iterative rollout or company leadership decides to change course again, the new software is already a thing of the past—even before it has been fully implemented.
By the way, here at Can Do, we’ve had the best results with a variation on the iterative principle: In our best practice, the software itself isn’t rolled out bit by bit; instead, it first undergoes a “test drive” with a select group of users. So it’s neither a “Big Bang” nor several small pockets of resistance, but rather a blazing fire of ideas. More on this in our next blog post. Here, too, the Can Do Migrator mentioned earlier helps this group get started with Can Do quickly.
Don’t want to wait any longer and would rather start migrating to the Can Do project management software right away? Then schedule an appointment today and let us advise you on the best way to implement Can Do. Just get in touch!
Our blog provides well-founded and practical content on project management, resource management, and the use of AI in businesses. Our goal is to equip professionals and decision-makers with tools, strategies, and inspiration to manage their projects and resources more efficiently and successfully.
Our new blog post series on hybrid project management, this time covering: top-down and bottom-up strategies, Big Bang ...
This time, in our new blog post series on hybrid project management: rolling out Can Do in five tried-and-true steps
The final post in our blog series on the rollout of Can Do: the first workshop, the requirements specification, and why ...