Martin Christensen
banner
holistictransformation.se
Martin Christensen
@holistictransformation.se
Product transformation coach, adult development theory aficionado, former user researcher/designer, author of Holistic Product Discovery, and always an Agilist.

https://holistictransformation.se

Personal profile: m8rt.bsky.social
Sorry för sent svar. Det ser skit ut överallt.
October 20, 2025 at 9:55 AM
Reposted by Martin Christensen
Once again for the people in the back:

'It's not a status meeting, it's a planning meeting: What is the best possible 'today' we can have?'
August 27, 2025 at 4:33 PM
I can relate very well. We can trace together. 😊
August 25, 2025 at 7:15 PM
Reposted by Martin Christensen
I assume you mean that humans are tools, which is entirely fair.
August 21, 2025 at 6:51 PM
Reposted by Martin Christensen
cats are a tool-using species, though!
August 21, 2025 at 5:47 PM
No. But it's next in line after what I read now. I have probably read everything else Pratchett... 😂
August 20, 2025 at 2:16 PM
Reposted by Martin Christensen
My account is now officially deleted so you can no longer read the post at the link above. Here’s what it said in case you’re curious.
August 18, 2025 at 5:14 PM
Reposted by Martin Christensen
This is all relatively easy when a company has the will to do it and genuine leadership (as opposed to management). A siloed company with command-and-control management and a focus on projects rather than the entire product probably won't be able to pull it off.
7/7
August 17, 2025 at 10:24 PM
Reposted by Martin Christensen
To do that, you must use an appropriate software architecture (see "Conway's Law"). Change must be easy.
* Create a work environment that puts people first. See Dan Pink's "Drive" and Richard Sheridan's "Joy Inc."
6/7
August 17, 2025 at 10:24 PM
Reposted by Martin Christensen
* Build exactly what's needed—not one semicolon more.
* Get feedback early and often, then immediately adapt and adjust to what you learn. That applies to both the product and your dev process.
* Quality is not optional—you work faster in bug-free code.
* Work incrementally.
5/7
August 17, 2025 at 10:24 PM
Reposted by Martin Christensen
* Work very small—ideally, you release at least daily to at least a subset of your users. The instant something is saleable, sell it.
* Focus on what your customers find valuable. Talk to them frequently and do that directly, not through an intermediary.
4/7
August 17, 2025 at 10:24 PM
Reposted by Martin Christensen
* faster idea-to-customer's hands ("lead") time
* happier employees, so low churn
* higher quality
* lower complexity (== lower maintenance and modification costs)

Disadvantages:
* (none)

So, how how do you get those advantages? Here are a few of basics:
3/7
August 17, 2025 at 10:24 PM
Reposted by Martin Christensen
You cannot be agile while at the same time slavishly following a set of prescribed rules, and if you're not agile, you cannot be Agile.

Advantages:
* lower risk
* faster revenue
* guarantee that you'll build something people will want (higher sales)
* lower dev costs
2/7
August 17, 2025 at 10:24 PM