Squirrel Squadron Substack

The Squirrel Squadron Substack blends insights on technology, leadership, and management, targeting tech and non-tech executives. It emphasizes collaboration between humans and AI, encourages questioning norms, and seeks to enhance team dynamics and innovation through strategic experimentation, intelligent disobedience, and understanding the business value in tech initiatives.

Technology and Innovation Leadership and Management Team Dynamics and Culture Strategic Planning and Execution Artificial Intelligence and Human Collaboration Software Development and Engineering Practices Product Management Business Strategy and Value

The hottest Substack posts of Squirrel Squadron Substack

And their main takeaways
0 implied HN points โ€ข 17 Dec 24
  1. Lewis and Clark faced a tough choice during their expedition and used small experiments to gather information before deciding which route to take. This shows the importance of testing different options when faced with uncertainty.
  2. In tech, instead of following rigid rules or 'best practices', teams should be flexible and adapt quickly. Fast iterations and feedback from customers are key to navigating complex projects.
  3. It's essential to create a safe environment where team members can learn from their mistakes. Viewing failed experiments as learning opportunities helps drive innovation and growth.
0 implied HN points โ€ข 17 Dec 24
  1. Graphs can help visualize motion and speed, making concepts like calculus easier to understand. It's fun to relate math to real-life activities, like driving a car.
  2. Machine learning improves by tweaking weights to reduce errors, similar to adjusting software for better performance. It's like steering a computer program to make it better.
  3. To build successful software, focus on small, frequent changes and measure how well they improve things. This method can lead to big wins in product development.
Get a weekly roundup of the best Substack posts, by hacker news affinity:
0 implied HN points โ€ข 17 Dec 24
  1. Many teams struggle to generate new ideas because they lack a clear strategy. It's important to have methods to inspire creativity and gather input from everyone, not just a few leaders.
  2. Informal decision-making can lead to power imbalances where only a small group influences ideas. This can cause confusion and make others feel left out of the process.
  3. To improve teamwork and idea development, it's crucial to establish clear processes and invite diverse voices into discussions. Transparency about who makes decisions can help everyone feel more engaged.
0 implied HN points โ€ข 17 Dec 24
  1. When looking at CVs, it's important to see what candidates did and why it mattered. Focus on real impact instead of fancy buzzwords.
  2. Many candidates use vague phrases that sound good but don't tell you anything meaningful. Look for specific results they achieved and how they benefited customers.
  3. A strong CV should show clear business results, like increasing sales or cutting costs. If it doesnโ€™t do that, it might not be worth considering.
0 implied HN points โ€ข 17 Dec 24
  1. Getting your eyes checked is more than just a routine; it includes numerous tests and trying on different lenses to find the best fit.
  2. Using advanced tools like a phoropter can help opticians quickly assess vision and find the right glasses.
  3. It's possible to create a more efficient optometry business that focuses on precise measurements and designs for better-fitting eyewear.
0 implied HN points โ€ข 21 Jan 25
  1. Racewalking is a competitive sport with strict rules, requiring athletes to keep one foot on the ground and their legs straight. This makes the sport challenging yet fascinating to watch.
  2. Just like racewalkers practice their skills for years, leaders should also work on their conversation techniques to build better relationships and trust in their teams.
  3. Improving communication takes effort and practice, much like training for a race. Small changes in how you talk can lead to big improvements in team culture and effectiveness.
0 implied HN points โ€ข 14 Jan 25
  1. Review your software supply chains regularly to avoid unnecessary risks. It's important to double-check any changes before they go live, especially in critical services.
  2. Understanding how computers work is crucial for software design. Sometimes, small mistakes can lead to big problems, so be careful how changes are made.
  3. In any organization, it's vital to prioritize tasks and not try to do everything. Maintaining focus can help avoid burnout and keep the mission on track.
0 implied HN points โ€ข 21 Jan 25
  1. Clarity in language leads to better understanding. When people use simple and clear words, everyone can see what's really going on.
  2. Avoiding the passive voice helps identify who is responsible. If we don't name who is responsible for actions, it can create confusion and misunderstandings.
  3. Being direct and open in conversations can bring out more ideas and honest discussions. When people feel free to speak openly, it leads to better problem-solving.
0 implied HN points โ€ข 14 Jan 25
  1. Always test your technology before using it in important areas like healthcare or finance. Relying too much on others without checking can lead to big problems.
  2. Small, controlled changes can help catch issues early. It's like testing a few canaries in a coal mine to make sure everything is safe before moving forward.
  3. Instead of blaming others when things go wrong, take a good look at your own systems. Make sure every part of your process is double-checked for safety.
0 implied HN points โ€ข 14 Jan 25
  1. The new tech podcast will feature conversations with business leaders on using technology creatively. It's an opportunity to learn directly from experts and ask questions.
  2. There's a unique opportunity for entrepreneurs in fintech or venture capital to solve problems for private equity clients. It's a chance to get involved in exciting projects.
  3. Emanuil's story shows that sometimes messy code can still be valuable in keeping a business alive. Focusing too much on making everything perfect can lead to problems, especially in startups.
0 implied HN points โ€ข 14 Jan 25
  1. Avoid doing a total rewrite of your software, as it often leads to mistakes. Instead, make small, incremental changes to improve what you have.
  2. Technical debt is a common issue in tech. Learning to manage and refactor it can lead to better software over time.
  3. Just as our bodies have remnants of evolution, software can have old parts that still serve a purpose. It's important to understand their history before trying to remove them.
0 implied HN points โ€ข 14 Jan 25
  1. In leadership, it's better to connect emotionally rather than just using facts. People respond better to stories and feelings.
  2. Trust is crucial when trying to persuade others. Use their language and ask real questions instead of just presenting evidence.
  3. In technical fields, bringing emotion and understanding business goals can lead to better teamwork and innovation.
0 implied HN points โ€ข 21 Jan 25
  1. We rely on many experts to prepare our food safely, from farmers to shippers, but we often overlook the importance of software engineers who also play a crucial role in this process.
  2. It's important to question and verify the work of those who create our tech products, just like we do with food safety. Ignoring potential issues could lead to serious problems later on.
  3. The speaker plans to host a podcast focusing on asking tough questions to industry experts, aiming to encourage others to do the same in their own workplaces.
0 implied HN points โ€ข 20 Nov 24
  1. Using synecdoche, or referring to a whole group by a part of it, can make communication more engaging and memorable. It helps in keeping language lively and can simplify complex ideas.
  2. Rewarding the whole team for their collective achievements is often more effective than just acknowledging individual stars. This promotes collaboration which is crucial for success.
  3. Traditional performance metrics and individual incentives can hinder teamwork. Instead, focusing on the overall outcomes and celebrating collective efforts can lead to better alignment and cooperation.
0 implied HN points โ€ข 20 Nov 24
  1. Instead of being a strict leader who just gives orders, it's better to involve your tech team in the decision-making process. This helps them feel valued and boosts their morale.
  2. Frequent updates and accountability are key. By having your team report their results often, you can help them stay on track and offer support when needed.
  3. Leaning back and letting your team take charge can lead to more action and better results. Itโ€™s important for them to demonstrate their value regularly, rather than waiting for orders from you.
0 implied HN points โ€ข 20 Nov 24
  1. Balkanization refers to splitting a region into smaller, competing parts, which can cause issues. In tech, dividing teams can create confusion and inconsistency.
  2. When tech teams work independently with different assumptions, it can lead to problems like bugs and compatibility issues. Teams should ideally work together to maintain a unified product.
  3. Maintaining a single product vision is crucial, so it's important to ensure that all teams align on the same goals and methods. This helps prevent issues down the line.
0 implied HN points โ€ข 20 Nov 24
  1. Active listening is not enough; you need to understand the deeper reasons and emotions behind what people are saying. This helps in making better decisions.
  2. Repeating back what someone said, including their reasoning and feelings, builds trust and reduces risks in communication.
  3. Learning to listen to and reflect on everyone's ideas, even unusual ones, is essential for teamwork and problem-solving.