Blog.
My musings on anything from leadership to technology to entrepreneurship and back.
User Story Maps
User-story-maps are essential tools for tech teams to visualize user journeys, prioritize features, and plan Minimum Viable Products (MVPs) efficiently. Let's checkout this essential tool.
Establishing Security In Tech Departments
This blog post outlines a structured approach to establishing security within teams, focusing on key elements such as security chapters, OKRs, roadmaps, and the role of security champions, with real-world examples from leading companies.
Brown Bag Sessions
Let's dive into what makes Brown Bag Sessions so valuable, and explore some examples of topics and companies that have successfully implemented them.
Two-Pizza Teams
Jeff Bezos crafted the term 'two-pizza team'. Let's see what it means and how you can use it in your organization to drive focus and growth.
Career Ladder
Let's talk about a simple and effective career ladder template that I've created. It's freely available and the perfect tool to improve hiring, performance management and defining salary ranges.
C4 Model
The C4 Model, is a framework for visualizing software architecture through four levels of detail: Context, Containers, Components, and Code, each providing a different perspective to enhance understanding and communication. Let's check it out!
Plan Like Amazon
Let's discuss planning cycles using Amazon's Operating Model, focusing on customer-centric goals, small teams, and regular reviews for optimal success.
Leading vs. Trailing Indicators
Amazon uses leading indicators to predict future trends and trailing indicators to assess past performance, ensuring proactive adjustments and continuous improvement. Let's check out how Amazon does it and let's dive into some examples
Understanding Test Coverage for Non-Techies
As Interim CTO I closely collaborate with non-technical folks. And often we come to the topic of 'test coverage'. For non-techies this concept looks very simple. High test coverage is good, low test coverage is bad. But it's not that easy - and forcing teams to produce a high test coverage will lead to disaster. Let's explore.
On 20% Time Projects
Your 20% time projects don't work? Here is how we revitalized our 20% time projects by scheduling them monthly, making participation optional, and enforcing rules for relevance, planning, and presentation. This structured approach improved focus, collaboration, and motivation across the team.
