Welcome to my blog!
Want to browse some models?
Just keep in mind:
“all models are wrong, but some are useful”
Yes that’s one of the quotes, I also have gathered a
few of those.
Or browse some of my notes from
Most of the models, came from one of these.
Maybe you’d like to read some juicy opinions?
I’m drawn to strong opinions, because
they [[opinion-strongly-expressed-opinions-help-me-discover-mine.md|help me discover my own]].
And recently, I started adding some of those to this blog.
Or some stories about teamwork, programming or
software development in general.
Or scroll down to see a small selection I made for you.
Positive discrimination: treat a candidate applying for a role more favourably on the grounds of the nine ‘protected characteristics’ – race, gender, disability, marital status, religion/belief, pregnancy, sexual orientation and gender reassignment (src)
Thinking about from a moral standpoint has not been that useful to me. I get caught up in multiple perspectives.
“If we don’t, the problem will never go away” “You should judge people based on merit” “It is patronising, implying those people don’t have the skills for the job” “It’s only fair” “It’s the opposite of meritocracy” … And that just causes me to get both judgy and lost....
In Book_ Toyota kata then mention the use of the Andon Cord. When they notice a quality problem, or a deviation off from the process standards, they pull it. This then halts the entire manufacturing line, and signals others to come. Then then swarm the problem in group, doing root cause analysis. They learn and improve the process, that is the goal.
It’s also mentioned that this cord is pulled about 1000 times per shift....
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....
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:...
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....
Video: PopcornFlow - Claudio Perrone ( https://www.youtube.com/watch?v=6L67Qu9fLu0 )
4, 5, incoming
1 = no option 2 = dilemma 3 = world of possibilities
innovation accounting week by week, are the actions I’m doing, useful?
--
Toyota improvement kata - mechanical measurement popcorn uses opinion ask before, ask after
--
second priciple how does popcornflow deal with unpopular opinions -> sell the problem better -> forget about your own, work on theirs -> I tried now, system was resistant, system changes after evolution, try again...
Video: Agile Essence and Fluency - Martin Fowler (https://www.thoughtworks.com/talks/software-development-21st-century-xconf-europe-2014)
Plan-driven mindset success = on time, on budget prevent change, stabilize/minimize it in the beginning
Agile mindset change is inevitable embrace change in a controlled way success = business value, improvement (harder to measure, organization scope)
x standard way across teams x standard story point to compare velocity amongst teams
After I decided to leave my current team, I wanted to say goodbye. In a beautiful way. I wanted to create a beautiful goodbye.
But I did not know how… (at the time I didn’t even have the words to describe what I wanted) So naturally, I ended up procrastinating and ignoring it, my default response to these types of situations.
Good thing I have a regular appointment with a therapist who knows to ask the right questions....