What a solid session — and a really good turnout. Thanks to everyone who joined and contributed to the FigJam mapping + dot-voting. Here are the key patterns that came through: 1) The “design tool” future looks hybrid, not a clean replacement Most of the group leaned toward a mix of visual tools + AI copilots, rather than “all-in code-first” or “same as before.” 2) AI is helping… but mostly as an assistive layer The dominant sentiment was: AI has changed workflows a little (speed-ups), not a total transformation for most people yet. 3) The biggest near-term shift is in research + synthesis When we asked where the shift happens first, the strongest signal was research & synthesis, followed by UI production. This matched the “Pain/Wish” notes too: people want better note-taking, transcript quality, and insight extraction from calls and research sessions. 4) The “PM/Designer ships everything” hypothesis: not fully true (yet) On “one person can ship a decent MVP end-to-end,” the room leaned toward somewhat disagree, with the bottleneck often being engineering realities, sustainability, and trust. 5) Collaboration is improving (quiet win) Most people said their dominant workflow is now designer + dev collaborating continuously (vs pure handoff). That’s a meaningful maturity shift. 6) Governance is the leadership topic hiding in plain sight The room leaned toward standardising an official AI tool stack to reduce chaos and risk. Biggest perceived risk: shallow thinking / low craft (moving too fast and not validating properly). 7) 2026 prediction: Figma stays central — but more focused The group’s expectation: by end of 2026, Figma remains central for core UI + design systems. And the most valuable people? Those who frame problems and lead alignment. Practical “next experiments” people can try - Choose one AI assist for research/synthesis (notes → themes → quotes) and test it for 2 weeks - Define a lightweight AI governance baseline (privacy, what not to paste, where outputs can be used) - Pick one workflow to tighten: Figma ↔ docs ↔ Jira ↔ dev handoff/integration - Add one quality guardrail: a “validation checklist” so speed doesn’t kill depth

Quick reflection from the closing round of our session yesterday: a few clear themes are already emerging for 2026. What members are focusing on this year: - AI in the workflow (practical, not hype): how people are actually using tools like Cursor / vibe-coding to move faster from idea → prototype. - Mentorship + the “mid → senior → leadership” gap: there’s a real need for support once you’re past “breaking into UX” and you’re stepping into leadership. - Design Ops + design influence: building an operating model, reducing silos, and increasing design’s impact in complex organisations. - Research access in specialist domains: how to test and recruit when you need niche users (not easy to find). Ideas for Lead by Design that came through strongly: - Create better awareness for potential members (that are not yet on the Skool community) - Partnerships with adjacent communities (e.g. IxDF) to grow the right kind of network - More sessions that are show-and-tell + workshop based, not just discussions Action: drop one personal goal, one work goal, and one Lead by Design wishlist item for 2026 in the comments. Let’s shape this year together. ☕️

As we wrap up 2025, I want to leave you with something practical you can use to close the year with intention and design the next one on purpose. I’m sharing Mel Robbins’ Best Year workbook as a resource for our community — it’s a simple, research-backed way to look honestly at your highs and lows, then decide what you’ll stop, continue and start in 2026. Use it in your own time over the next few days, and if you’d like to share any reflections or intentions for 2026, this thread is the place. Thank you for being part of the first chapter of Lead by Design — can’t wait to see what we grow into together next year. 🌱✨ Until next year! Jaco

Yesterday’s Coffee Hour surfaced two big themes that I think many of us are feeling right now. 1. The rise of the “team of one”We spoke about how AI is accelerating the convergence of roles: UX, product, UI, even front-end dev. In smaller teams and startups, one person can now realistically take a product from idea → design → prototype → build → customer feedback with AI as a co-pilot. That’s exciting… but it also raises questions: - How do we position our value when we’re being asked to “do it all”? - What do we stop doing, so we don’t burn out trying to be designer, PM, dev and support at once? 2. Changing UX maturity without saying “UX maturity”We also dug into the reality of working in low-maturity environments where UX is still seen as “making things look nice”.A key insight: sometimes the most effective way to shift an organisation is to do the work under a language they already accept – things like: - “Let’s map the roles so we can write better user stories” (→ personas) - “Let’s walk through the end-to-end flow” (→ journey mapping) You don’t always have to fight for the label “UX” to start changing how people think and work. Showing the value first, naming it later, can be a powerful strategy. Over to you: - Where are you feeling the “team of one” pressure right now? - Have you ever smuggled good UX practice into a low-maturity environment under a different label? What worked (or didn’t)? - Drop your stories and reflections below – this is exactly why Lead by Design exists. 👇

Hi Lead by Design Community This year both Christmas Day and New Years Day fall on a Thursday - our usual Coffee Hour time slot. So we'll be taking a 2 week break at the end of 2025, and will resume our Coffee Hours again on Thursday 8 January 2026. Wishing you a blessed holiday season 🎅