Learning Loop

Product People!! There's less than 2 weeks to go. We’re back with a topic that’s hard to ignore right now: Team Topologies in the age of AI Two top-notch speakers: - Jesper Just Jensen on restructuring real-world product orgs - Kasper Junge on how AI is already reshaping how teams work If you care about how product teams are structured, and how that’s about to change, this one’s worth your time. 🍻 Free bar, sponsored by Copenhagen Product Collective 👉 Join us: https://lnkd.in/eaKhDuXc

We hope to see you in Copenhagen on April 14th!

Customer Onboarding is not a checklist. It’s a race to the first meaningful result. If users don’t experience value early, nothing else matters. No tour, no tooltip, no clever UX pattern will save you. The moment it clicks is everything. Read our latest article on good user onboarding: https://lnkd.in/eRYZJtUx

Most teams think onboarding starts after signup. That’s already too late. By the time a user enters your product, they’ve already decided what it does and why they’re there. And if that expectation is even slightly off, your onboarding flow is now working against it. This is why so many onboarding experiences feel heavy but still underperform. The real issue starts earlier. At the very first touchpoint. That’s where users form their understanding. That’s where you either align them or lose them. And that’s what defines whether onboarding will work at all. Most friction isn’t in the UI. It’s in the interpretation. I wrote a short piece on how onboarding actually begins before the product, and how “selling the outcome” shapes both conversion and activation. https://lnkd.in/eHFdJw_U

This one encompasses much of what I've learned the last 10 years developing, testing, and using the Persuasive Patterns card deck. https://lnkd.in/eHHaJKsJ

New on the UI Patterns blog: People choose the path of least effort. When interaction cost is high, even motivated users hesitate or drop off. Reduce the effort required to complete tasks and behavior becomes more likely. A short read on measuring and minimizing interaction cost in UI design. https://lnkd.in/ekYj68jn

We used to blame fragmentation on large product teams. Now small teams are seeing the same thing. AI and vibe-coding speed everything up. One person can design, build, and ship. But without structure and shared context, each prompt becomes its own decision. The product still works. The experience drifts. What used to happen across departments now happens inside a single workflow. Same pattern. New tools. Fragmented user experiences. https://lnkd.in/expkqatg

As teams scale, products often fragment. More teams solving local problems = more seams in the experience. The way out isn’t more alignment. It’s designing shared capabilities across teams instead of isolated features.

I hope I'm going to see you Wednesday this week at the product loop meetup on scaling! Here's a small, but very important update: the venue has moved! We'll meet at: Saga (boat) Havnegade 31Z – Kajplads 140 1058 København K sagaboat.dk Time and program are unchanged – we’re just meeting on the water instead of at H9. If you’ve already signed up, your registration is still valid. If you haven’t, you can still join here: https://lnkd.in/ePMxdNB6 Looking forward to welcoming everyone on board Saga.