I’m a project manager who can’t stand pre-built project management solutions. Churches use them, businesses use them, but frankly, they’re just not as helpful as we act like they are.
I used Microsoft Project. I’ve seen and used cloud based project management solutions—many of the ones available on the market. All the options frustrate me and waste my time. They each taught me something about my process and I’m certainly a better project manager for it, but they each led me to force projects into molds and ultimately inhibited workflow. Here are three reasons why you should create your own project management solution(s).
1. Smart people don’t need every task written out for them.
Writing out milestones and dependent tasks is essential for every project, but writing out every task isn’t. Many project management technology solutions require that every task be written out. (And even if they don’t require it, they make you feel like you should.) I have found myself spending hours writing out tasks when I could be accomplishing things. If you work with smart people, why do you need to write out every task? I work with smart people, so why would I force people into my style of a task list? Having one task list master also makes others feel small and bossed around. I want to work with others because of who they are, not force them to think like me. In addition, ridiculously detailed lists created by “supervisors” are for people who want to check boxes. And people who check boxes will never lead in a meaningful way.
2. To successfully innovate, efficiency must be gained.
The easiest way to save money is to spend less. Bringing in sales is far more difficult than not spending money. For these reasons, the easy solution, which seems cheap, is to adopt someone else’s pre-built system. But doing so will actually cost you more money. It will constrain you. Innovating is already difficult. If you impose someone else’s constraints and methods on your work, you will just make it more complicated. You need efficiency. Create it by making systems for your new process. Don’t lose efficiency by forcing your new process into a machine made for something else or created with variables you don’t need.
3. One-size-fits-all systems can’t accommodate substantial change.
When you adopt a technology solution for project management from someone else, you’re imposing a framework that can’t easily adapt. When you use someone else’s system, you don’t know how it was built, so how can you change it? Things will change and the system must change with you. If your projects are creative, they probably have some flexibility to them, which means you will need to prepare for the inevitable change. You also need to prepare for the human element: changing things because they’re not working. Adaptability is easy when the entire system’s creator is the user(s).
I wish project management was as easy as downloading an app, but it’s not. Systems must be built to accommodate us and our projects—sometimes per unique thing and almost always per unique team. This doesn’t mean you can’t reuse frameworks or have a process—you definitely should do both—but it does mean that you should be cautious when adopting someone else’s. They’re not you. Be unique. Make your own system.
What project management system do you use? Did you build or buy?