Wiki’s should never run your projects. They are a starting point, perhaps an informal collection of ideas. But once you start committing tasks to them, and putting work onto them you’ve now tasked yourself with the role of constantly updating them to show progress when what you should be doing is delivering the work to get done. Once you start managing the tasks and their display, you’re no longer doing your best work.
The journey is the memory we talk of. It’s the in-between moments of everything that comes together when it comes together, and how it comes together. It’s the small stories that we reflect on and remember without hesitation. It’s the best of us and when we get to the destination, all we talk about are the bumps and adventures that happened in the journey. Don’t miss out on the journey, it’s not worth forgetting.
If you can’t handle the downs or act the same way when things go wrong. You probably don’t deserve the success or the wins that come along with it. Anyone can lead in the best of times, anyone can lead when things are going well. It takes a special few who can lead when things are going wrong.
What you do, how you talk, how you move, and what actions you take. These are the examples you set for what you do. They are what define you, they are what people know you for, and they are how you are remembered. If you’re worried about how you are being perceived, maybe start there, in what you are doing, today.
If your framework is overcomplicated, if it requires many steps to get up and running. If the space between start and success is a long battle fraught with many discussions, forum posts, and chats to get there. Chances are adoption won’t happen as quickly as you want it to. Adoption, in any framework, is key and critical to design. If people can’t easily get into it, it doesn’t matter what it can do.