Martin Christensen

Sorry för sent svar. Det ser skit ut överallt.

I just saw someone use the abbreviation “AI;DR” and I’ll be laughing for a while.

all discourse aside, there is one machine with consciousness. it's printers. they are alive and conscious and they hate you and they'd take your arm clean off if you let them. never trust a printer.

Great teams are less like awesome machines and more like awesome organisms. - Team of Teams

Slightly diminish a book

Interviewing a user

The attached graphic is an excellent summary of everything that a good Product person does. You will note that "_project_ management," "manage tickets," "compel or browbeat people to build X," and "use Jira" are nowhere to be seen.
1/7

enshittification | noun | when a digital platform is made worse for users, in order to increase profits

I want as many developers as possible to experience the joy of refactoring their code when they have a good test suite by their side.

It's infectious. You'd want that feeling all the time.

Everyone has been trained to get high fidelity prototypes. I worked with a new team and they were hounding me on high fi artifacts to run research and I said let’s see how the research goes first. The research yielded changes so to spend all that time on the minutiae would have been a waste of time.

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?'

“I worked on 2045. I’ll continue that. I have no blockers.”
“I worked on 3122. I’ll maybe finish that tomorrow. No blockers”
“I finished 2066, then started 2173. No blockers”
“I worked on 2754. Still on it. No blockers”
“I did 2355. Still on it. No blockers”
“I just started 2039. No blockers”

I can relate very well. We can trace together. 😊

In this article, @lauraklein.bsky.social points out all the reasons organisations have for not doing the research and keep delivering things with low value, as well as the true underlying cause. Read it!

https://www.nngroup.com/articles/why-organizations-dont-do-user-research

I assume you mean that humans are tools, which is entirely fair.

cats are a tool-using species, though!

No cat has ever caught a tuna. It should not be food for cats. Yet cats love tuna. Makes no sense.

No. But it's next in line after what I read now. I have probably read everything else Pratchett... 😂

Can my subscribers pay on the Substack iOS app? Substack now includes external links in the iOS app that take readers to the web to complete their purchase. Subscriptions made this way are treated like standard web purchases—creators receive the...

Attention chumps: If you, despite all our dire warnings, decided to put your newsletter on Substack, the untrustworthy asses who run the company just did what we all knew they would, and made it impossible to take your subscribers with you if you want to leave. support.substack.com/hc/en-us/art...

screenshot: After much reflection, I have decided to leave Substack. Thank you so much for subscribing, and for reading my work. I appreciate your time, encouragement, and support. Rest assured that this decision has nothing to do with my commitment to writing fiction. I recently finished my 32nd short story and crossed 57,000 words on my 3rd novel. I write every day. After a close analysis of the alternatives, I've decided against continuing to share my fiction via a newsletter format. I started using Substack because I believed it might help me to find a literary agent, and then a publisher for my novels and stories. While I am now represented by Liz Nealon, the brilliant founder of Great Dog Literary, I no longer believe sharing my work in this way will help me to find a publisher, and may in fact hurt those efforts. I will continue to be a daily user of Bluesky. Stay tuned there for future updates regarding where you can read my work!

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.

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

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

* 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

* 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

* 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

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

Was asked: What are the pros and cons of an "Agile" approach? Here's my list, but bear in mind that I am NOT talking about Scrum or SAFe or Kanban. I don't see those frameworks as even slightly Agile, at least not inherently.
1/7

I might be delusional because I've grown up and live in Sweden, but I think you need to take a longer break.

Komplexitetspodden Technology Podcast · Updated Weekly · En podcast där tankar om komplexitet får fokus en stund.

It's alive! Komplexitetspodden (The Complexity Podcast) is now available at Apple podcasts.apple.com/us/podcast/k...

...and at Spotify: open.spotify.com/show/40Cpa7M...

First episode: Enkla regler (Simple Rules). A new episode, featuring a unique theme, will be published every Thursday.

Your job is to help your customers (at least that's the way to create a product they want to buy). Your job is not to invent stuff out of whole cloth.
2/2

I often hear "The customers will *love* this!"

No. They won't.

Customers will happily tell you what they need. They do that every day when they call tech support, for example. Talk to them. Pay attention.
1/2