🚀 Antoine van der Lee

’ll be honest, I didn’t see the point in narrating decks at first. I thought replays were “good enough.” Then Femke walked through how Copilot uses memory and saved instructions, and how you can spin speaker notes into a short, shareable video. It clicked. I was measuring the wrong thing. Most replays sit in inboxes. Context moves work. So I changed my approach: delete the replay; deliver the why, what, next. How I run it now: ✅ One clean deck per initiative. ✅ Draft narration with AI. I tighten it to my voice. ✅ Pull actions and owners while the context is fresh. ✅ Add a five-line decision log so the “why” doesn’t vanish. It’s faster to consume. Easier to hand over. Clearer on who does what, by when. That’s the value of these conversations. You think you’ve made up your mind about a solution. Then someone shows a use case that shifts it. If you wrote Copilot off, maybe give it another look. The potential is broader than I gave it credit for. 👉 Full chat with Femke on Impact of AI:Explored is live. Link is in the first comment #EUC #UserExperience #AI #ProductMarketing #ImpactOfAIExplored #Liquidware PS: Found value here? Repost ♻️ to your network and follow me for more.

12

3 commentaren

"Hiring top teams without structure is like building code without an architecture." That was my core takeaway from our DoubleDutch scale-up story. I learned fast: - Explicit role definition matters: Before plugging someone in, map what they own and what remains untouched. That clarity prevented the easy button trap. - Trust is engineered, not assumed: Matt came from our intern ranks, he already knew the founding rhythm. That preexisting trust made him effective from day one. - Quadrant structures accelerate onboarding: I referenced a simple principal + leadership + org + strategy framework. It built shared visibility and reduced friction. - Technical precision in strategic decisions: Whether modeling the next office, M&A readiness, or pricing analysis those cross functional junctures reveal gaps. That's where meaningful impact happens. Scale isn't just about moving fast, it's about ensuring every function runs on the same blueprint.

36

2 commentaren

The biggest lie experienced developers tell themselves: "My work speaks for itself." No, it doesn't. Your work whispers in private repositories while other developers shout their value from the rooftops. I see this pattern everywhere: • Brilliant engineers working in silence • Average developers building audiences   • The quiet ones getting passed over for promotions • The vocal ones landing leadership roles It's not fair. But it's reality. Here's what I learned from 7 years in tech: Visibility beats ability when ability isn't visible. You could be the best architect in your company. But if the CEO doesn't know your name, you're invisible. You could solve the hardest problems. But if you don't share how you solved them, nobody learns. You could have the deepest expertise. But if you keep it to yourself, it dies with your career. The developers who get promoted, headhunted, and recognized aren't necessarily the smartest. They're the ones who make their intelligence visible. They document their decisions. They share their learnings. They teach others their methods. They build relationships across teams. Your expertise is worthless if it's locked in your head. Your experience is meaningless if nobody knows about it. Your skills are invisible if you never demonstrate them publicly. Time to change that. Start small: • Answer one question in a developer forum • Share one lesson learned this week • Comment thoughtfully on technical discussions • Write about one problem you solved Your work is amazing. Now help the world see it. What's stopping you from sharing your expertise?

24

9 commentaren

In this episode of Founder's Code, Janus Klok Matthesen — Co-Founder & CTO of Pixelz Inc, shares how he built and 𝐬𝐜𝐚𝐥𝐞𝐝 𝐚 𝐠𝐥𝐨𝐛𝐚𝐥 𝐛𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐨𝐯𝐞𝐫 𝟏𝟒 𝐲𝐞𝐚𝐫𝐬. Pixelz works with thousands of clients worldwide and processes tens of thousands of images every day, operating under strict deadlines with zero room for error. 𝐇𝐞𝐫𝐞’𝐬 𝐰𝐡𝐚𝐭 𝐬𝐭𝐨𝐨𝐝 𝐨𝐮𝐭: 🔹 Why 𝐩𝐫𝐨𝐝𝐮𝐜𝐭–𝐦𝐚𝐫𝐤𝐞𝐭 𝐟𝐢𝐭 is the real line between scaling and knowing when to pivot 🔹 How 𝐠𝐥𝐨𝐛𝐚𝐥 𝐠𝐫𝐨𝐰𝐭𝐡 𝐫𝐞𝐬𝐡𝐚𝐩𝐞𝐬 𝐥𝐞𝐚𝐝𝐞𝐫𝐬𝐡𝐢𝐩 and day-to-day decision-making 🔹 What it actually takes to 𝐫𝐮𝐧 𝐭𝐞𝐚𝐦𝐬 𝐚𝐜𝐫𝐨𝐬𝐬 𝐄𝐮𝐫𝐨𝐩𝐞, 𝐭𝐡𝐞 𝐔𝐒, 𝐚𝐧𝐝 𝐀𝐬𝐢𝐚 🔹 How COVID stress-tested the company’s culture, systems, and leadership 🔹 Why Pixelz chose radical transparency and shares company numbers internally 🔹 How 𝐀𝐈 𝐫𝐞𝐦𝐨𝐯𝐞𝐝 𝐨𝐯𝐞𝐫 𝟔𝟎% 𝐨𝐟 𝐦𝐚𝐧𝐮𝐚𝐥 𝐰𝐨𝐫𝐤 — without replacing people If you’re building or scaling a company, this episode offers a grounded, experience-driven look at what that journey really involves. 👉 Full episode here: https://lnkd.in/gzNKcrTj

12

1 commentaar