English Blogposts on Klaus Breyer

Our travel videos live on a Raspberry Pi.

“We need to build a follow-up feature for the letters the relatives get from the social welfare office.”

What a time to be alive.

There is a new Shape Up book, and it is written by an enterprise practitioner.

My wife and I have blogged about every trip since our honeymoon 10 years ago.

Three people have three lines of communication.

Today I want to share about the trip with my wife to Mexico.

Here is a pattern I have seen too many times: A designer produces 100 Figma screens.

Every dictionary word .com is taken.

A few months ago, the team had a thorough discussion about our git workflow.

This morning, one of our engineers spent 45 minutes with a candidate.

Because we now live in times where you can build a solution faster than you can spend time being annoyed about the problem, I built imaedge.

In the previous post I shared the keynote that opened our two-day team offsite: a barrage of theses on how AI changes the product development lifecycle.

This week I ran a workshop with my team.

Developers and designers each had four tickets in progress at the same time - and by “in progress,” I mean actually in progress: including tickets in review and tickets in testing.

My son is absolutely fascinated by the scales in the fruit and vegetable section at Kaufland - the ones that print those little stickers with prices and barcodes.

I hadn’t hired anyone in a year.

Today I’m speaking at ML Week Europe in Berlin. edding: Bridging the AI-UX Gap in B2B SaaS through Interdisciplinary Collaboration Machine Learning adds complexity to product design—not just in implementation, but even more during product discovery, where…

Today I’m speaking at the code.talks conference in Hamburg!

Today I’m speaking at Agile Prague about a topic that lies at the heart of modern product development: why tickets create silos – and how we can move beyond them to unlock true interdisciplinary collaboration.

Today I want to share about the trip with my wife to French Polynesia.

“Building software is a design process.

I taught a masterclass for CTOs of the alphalist community: Distributed, Yet Focused – High-Impact Remote Teams Remote work isn’t a challenge – it’s an advantage.

Let’s start with one of my favorite quotes: Organizations [that design systems] produce designs that mirror their communication structures.

Building software is fundamentally different from manufacturing.

I’ve ranted about Teams often enough.

Lets start with a quote: Agile now means, we do half of Scrum poorly and Use Jira.

Let’s rewind to 1913.

I recently joined Zuzi Sochova’s #AgileWay podcast for a short and sharp conversation on agile practices in interdisciplinary teams — with a nod to my upcoming talk at AgilePrague.

I taught a masterclass for CTOs of the alphalist community: Move Fast and Break Silos - Leading Interdisciplinary Teams and Organizations 🎨 Software isn’t manufacturing with specialized disciplines—it is supposed to be an interdisciplinary design process

After three years and 42,000 km from Copenhagen to Maranello with the IONIQ 5, I’d like to share my experiences – the good, the not-so-good, and the reasons why I’ve now decided to get a new car.

While managing product & tech at edding AG, my work sometimes spans from the strategic to the operational level.

In Startup Phases For CTOs, Stephan Schmidt outlines the core phases startups go through and what CTOs should focus on in each: ideation (generate ideas, talk to potential customers, resist coding and building castles in the sky), prototype (sell early, s…

In Rewilding Software Engineering, Simon Wardley and Girba Tudor explore software engineering as a decision-making process about systems that are too large for us to fully grasp.

In From Project to Product Mode, Sebastian Borggrewe and Thomas Hartmann outline seven challenges for shifting from project to product mode: segmentation (homogeneous customer segments), pricing (individual requests highly priced), product discovery (filt…

In Engineering Role Descriptions, Stephan Schmidt provides guidance on creating clear role descriptions for engineering teams.

In Developer Accountability, Stephan Schmidt provides practical techniques for holding developers accountable.

In Click, Jake Knapp and John Zeratsky provide a practical framework for building products that actually work—products that “click” with customers.

I for sure knew designers and engineers didn’t think the same way.

It was just the usual mess: The product team had merged a couple of months before, inheriting a codebase from an agency working on a shoestring budget.

There was a time when I managed some individuals who weren’t particularly independent.

Marty Cagan has been vocal in his books and online about his belief in co-locating empowered product teams.

I know how important solid coaching skills are for any leader.

Let me share a recent story from a real project.

I am always amazed to think that people 6,000 years ago were not so much less intelligent than we are today.

Conferences are everywhere, but some stand out.

Ensuring the security of your WordPress content is essential, especially when sharing sensitive information.

Effective planning and organization are crucial for team productivity.

Organizing workshops and group activities often requires randomizing participant lists to ensure fairness and engagement.

First, the key dates: 25.07.2024: Toraja 30.07.2024: Rammang-Rammang & Leang-Leang 31.07.2024: Bangka 07.08.2024: Return journey Arrival ¶ Traveling to Indonesia or Southeast Asia always has two key moments for me: Moment 1: When you suddenly become the “…