Jon McLaren

The new 2025 Digital Accessibility Index shows a worrying pattern: many companies still struggle with the basics — navigation, readability, usability. It’s a reminder that accessibility issues aren’t edge cases. They’re systemic. When design misses the fundamentals — clear structure, consistent controls, readable content — trust quietly erodes. I often see teams polishing what’s visible while the foundation cracks underneath. And when the foundation wobbles, everything above it does too. If you ran a quick scan of your site right now, how many hidden accessibility gaps would it reveal — before your audience does? I have no affiliation with either of these sites: Basic free scan: https://lnkd.in/gu_wQDqe Technical free scan: https://wave.webaim.org/

23

6 Comments

Great article Matt Rothenberg and I totally agree that there's not much out there about guidance for agents when it comes to compositions and templates. Totally agree with this quote: "A component library gives builders reusable parts; a design system makes recurring decisions about structure, behavior, and user interaction canonical. When those decisions live only in a shipped screen or somebody’s head, agents expose the gap quickly: they build from what you encoded and make reasonable but different inferences everywhere else." https://lnkd.in/eBBn8Uqd

12

I’ve spent a lot of time working alongside CRO teams. The reality is, a lot of that workflow ends up living in Notion. Audit after audit. Insight after insight. Experiment ideas, priorities, impact estimates… all documented manually. So I had a thought: What if the tool did the work for you? That’s where Auditly came from. A concept for a CRO intelligence tool that takes you from: → Audit a page → Identify friction → Prioritise opportunities → Recommend what to fix first → Turn recommendations into experiments → Keep a history of everything Basically, less time maintaining the CRO system and more time actually improving the experience.I designed and vibe-coded the whole thing in Claude — in a day!! Had a ridiculous amount of fun making this. You can play around with it here: https://lnkd.in/gapTG6gN One caveat: this is purely a design/prototype concept. The scores, recommendations, and data are mocked — there’s no real auditing engine behind it (yet 😉) Would love to know: what’s a repetitive part of your design workflow you’d love to have a tool do for you?https://lnkd.in/gapTG6gN One caveat: this is purely a design/prototype concept. The scores, recommendations, and data are mocked — there’s no real auditing engine behind it (yet 😉) Would love to know: what’s a repetitive part of your design workflow you’d love to have a tool do for you?

27

12 Comments

If your SaaS isn’t converting… It’s not always a marketing problem. It’s often a UX problem. Confusing flows Weak CTAs Poor onboarding Too many decisions Small UX fixes = big revenue impact. If you’re building or redesigning a product in 2026, let’s talk before you invest more in development. Comment “Audit” and I’ll share what I’d check first. #SaaS #ProductDesign #StartupGrowth

1

Agentic AI risk is not (only) about chatbots saying weird things. It's about giving software enough context and initiative to become part of the operating model. Figma’s post on using agents to stay ahead of vulnerabilities is a good signal: agents are moving from side experiments into security work itself. We used to have a human team using tools. Now, we have humans supervising delegated action across queues, tickets, decisions and evidence. An AI agent is a junior operator with API access, not a smarter search box. Picture a vulnerability queue where an agent triages issues before a person has even opened the dashboard. Security, privacy, risk and GRC leaders need ownership, permission boundaries, logging and exception handling before the agent becomes invisible infrastructure. Controls before choreography. https://lnkd.in/erQacC8f

2

Hot take, dear designers and founders; If your UX feels broken, your design is probably not the problem. Your thinking process is. Why do we create wireframes before final mockups? Let’s be honest, many designers jump straight into Figma. No idea validation. No sketches. No low or mid-fidelity designs. Just polished screens. Then the frustration starts: Why is the UX not smooth? Why am I stuck? Why does this feel wrong? Wireframes exist to help you think, not to impress stakeholders. They bring clarity to: • User goals • Information hierarchy • User flows and edge cases When you skip wireframing, you’re designing with assumptions not insight. Yes, if you’re working on an existing product, some steps can be shortened because patterns and data already exist. But when designing a new solution, there is no shortcut. This is something I always stress in my Product Manager classes at Enoverlab: If you don’t validate the idea first, you’ll waste time and resources, and spend even more fixing problems that should never have existed. Wireframes aren’t optional. They’re a risk-reduction tool. Design fast. But think first. Curious to hear your take: Do you still wireframe before jumping into high-fidelity designs, or do you go straight to final mockups? #UXDesign #ProductDesign #Wireframing #DesignThinking #UserExperience #ProductManagement #DesignProcess #StartupDesign #SaaSDesign #DesignLessons #UXStrategy

15

2 Comments

Most technical writers think in files. Git thinks in changesets. That gap is why commits feel messy, PRs get confusing, and engineering teams don’t always take documentation seriously. The fix isn’t learning more commands. It’s a mindset shift — from editing files to managing documentation states. In Part 3 of my Git & GitHub for Technical Writers series, I go into exactly that: — What a “documentation state” actually means — Why atomic commits make you easier to collaborate with — How reversibility gives you editorial courage — How version thinking aligns you with the development lifecycle This is for technical writers working in Docs-as-Code environments — or preparing to. If you’ve ever pushed a commit with the message “updates” and felt vaguely embarrassed about it, this one’s for you. 🔗 Read Part 3 here: [https://lnkd.in/dvJv-FAZ] 💬 When did Git finally click for you — or are you still wrestling with it? #TechnicalWriting #DocsAsCode #Git #Documentation #CareerGrowth

3

Most UX problems aren’t design problems. They’re system problems. Disconnected flows. Layered decisions. Legacy logic nobody wants to untangle. When you clean the system, the experience fixes itself. That’s the work.

1