Phrases like 'Work smart, not hard' and 'Quality over quantity' sound appealing but are empty without practical application. In this newsletter, let’s explore how these concepts can transform your approach to work, especially in the realm of software development, by applying the principles from Benjamin Hardy's "Who Not How."
I've always believed in tackling challenges independently. Consider the task of creating a website for my local chess club. My plan involved several steps:
Frontend: Setting up a React project seemed straightforward.
Backend: AWS/Firebase for backend operations.
UX/UI: Drawing inspiration from Dribbble for design.
Sales and Promotion: Utilizing online resources for marketing strategies.
Support: Implementing a reliable system like ZenDesk.
This method, where I address each aspect, echoes a traditional mindset: if you have the skills, why not do it all?
However, as Hardy suggests in "Who Not How," this approach often leads to inefficiency. It's not just about whether I can complete these tasks, but if it’s the most effective use of my time and skills.
Pareto's Law, or the 80/20 rule, reinforces this idea. But how do we translate it into action? Hardy proposes a significant shift in thinking – from HOW to WHO.
In the tasks listed above, I initially focused on how to achieve each goal. This approach means spending time on designing solutions, choosing tools and technologies, and actual coding and debugging.
While this might seem efficient, Hardy challenges us to consider if it's the best use of our time.
Practical Example
Let me share a personal experience.
Recently, I embarked on an exciting project, that should be released mid-January.
Right from the beginning, my partner,
This strategy proved transformative. By delegating effectively, we completed the backend ahead of schedule, allowing us to redirect our energies efficiently. Embracing the 'WHO' mindset not only accelerated our progress but also ensured that each aspect of the project was handled by someone with the right expertise, greatly enhancing the overall quality and efficiency of our work.
The 'WHO' doesn’t have to be only for people who are creating projects of their own.
There are plenty of team leads who feel like they have to take everything on themselves and not delegate. That is a great place to ask yourself Who can do that better than me? Or at least good enough so I can attend more important things.
Keep in mind: Once you have a WHO to do the work for you, you need to give them space and avoid micromanagement. Remember, you hired them because THEY ARE the experts, not you.
While hiring help involves costs, it's an investment in efficiency and quality. The alternative to it is spending time learning and doing it all yourself, which might not cost money upfront but can cost your future self in terms of time, motivation, and missed opportunities.
Final Thoughts
In conclusion, by embracing the 'Who Not How' philosophy in our work, we open ourselves to a more efficient, productive, and enjoyable way of accomplishing tasks. This shift in mindset, inspired by Hardy's insights, is not just about making our workflow easier and more fun. it's about enhancing the overall quality and impact of our projects.
So, the next time you're faced with a task, ask yourself:
Can someone do this better, faster, or more efficiently than I can?
By adopting the 'WHO' not just the 'HOW' in your workflow, you can change the trajectory of your projects and achieve greater success.
Thanks for introducing this one to me :)
I definitely have this tendency, it's very temptimg. 10-15 hours of a udemy course and we can do pretty much anything in a ~solid level. Using experts brings much better results, and definitely worth the money if you want to create something not mediocre.