Published

Before: There are 3 services, part of a product. The users of the system, need to interact with all 3 services. There is no unified way / place for interacting with all 3. Each system is owned by a separate team. Both the users and the services are internal to the company. Assignment: Create a single point for the user to interact with the system (instead of 3) Rethink the way users interact with the product, so it closer matches the product vision....

postmortem has 3 important jobs explain what happened apologize commit to improvement anomalies and root cause we look for causes, and any anomaly either get's labeled as a root cause or a contributing factor many times these anomalies are present during "ordinary operations, too. We give them more weight that they deserve anomalies are present all the time learn from “near misses” eg. type an incorrect command, but catch it before executing...

Out-learn the competition Is learning and continuous improvement the main strategy? Out-produce the competition Is focussing on producing more, working harder, … the main strategy? (src: Book: Toyota Kata)

Pro Easy Quick win Con Never want to remove them Become dependent Limiting Don’t learn the essence: improve & adapt Can’t improve on it Pro - Easy It’s easy to copy something in it’s whole at first. Imitation is how most learning happens (Model_ Shu Ha Ri) Pro - Quick win Never underestimate the value of a quick win. It goes a long way towards convincing people! Con - Never want to remove them People think: “It works, why fix it?...

You can’t learn while you blame others. You can’t learn while you blame the system. You can’t learn while you blame the world. You can’t learn while you blame yourself. (aka shame) When you blame, you put the power for change somewhere else. Blame mindset: You have a problem. [Some person / thing] is to blame for that problem. [That person / thing] needs to change, for your problem to be solved There is nothing you, yourself can do but wait and complain No learning happens Shame mindset:...

When I was about 12 years old, I bought a Java book with my first allowance. With books and the internet, I taught myself how to code. Initially I recreated small games, but over time also started creating small utility programs for myself. I programmed by myself for years. I learned, the need for maintainable code, the hard way. I was building this game my brother and I came up with....

The following story from before the Second World War, when Toyota made weaving looms, provides an example of this way of thinking. It comes from a Toyota booklet about the spirit and ideas that created the company, and relates how Kiichiro Toyoda (1894–1952), founder of the Toyota Motor Corporation and son of Toyoda Automatic Loom Works founder Sakichi Toyoda, supposedly responded when someone once stole the design plans for a loom from the Toyoda loom works:...

fluency / flow - where is the toilet/ how much does this cost - get around in a city / ask & answer some questions / who is there - tell a story - give a speech - debate / teach abstract concepts any level of fluency can be the right amount (src: Video_ Dancing Along the Agile Fluency Path - Diana Larsen)

It all happened at once: a new job, needing to pay rent, needing to pay my own taxes, insurance, … I don’t remember all the steps, but I do remember parts of it. Version 1 - just keep a healthy buffer The idea here is that you don’t really know what the unexpected costs will be. But you keep enough of a buffer, so if any come up, you can pay them without any debt....

I have this value stream for reading. Reading valuestream But the mapping part is always very labor intensive. While reading I create highlights, but most note taking apps are quite limited in the colours. Kindle only allows four, and that’s one of the better ones. Many have only one colour. And even 4 static colours, started becoming too inflexible for me. So I decided to make my own ebook reader app....