Activity
Mon
Wed
Fri
Sun
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
What is this?
Less
More

Owned by Jaco

Lead by Design

11 members • $6/m

A community for design leaders (and aspiring design leaders) mastering user-centered innovation, strategic leadership & driving impact at scale.

Memberships

AI Profit Boardroom

1.8k members • $49/m

AI Money Lab

39.4k members • Free

Skoolers

181k members • Free

27 contributions to Lead by Design
🎨 UX Designer Burnout: Freelancers vs. In-House: What’s Really Going On?
Burnout hits designers hard, but why it happens depends heavily on where you work. Freelancers and in-house designers experience creativity, pressure, and exhaustion in totally different ways — and understanding the differences helps us protect our energy, our craft, and our careers. Freelance Designers: Freelancers carry everything on their shoulders: design, marketing, client communication, billing, deadlines, revisions, and boundaries. The freedom is amazing, but the cost can be high. Irregular income creates pressure to say yes to everything. Clients bring unclear briefs, sudden direction changes, and scope creep. And since freelancers often work alone, there’s little feedback or collaboration to recharge inspiration. Burnout shows up as exhaustion, self-doubt, and feeling “on call” 24/7. Autonomy is high — but so is ambiguity. In-House Designers: Company designers have the opposite problem. Work is structured, deadlines are defined, and teams provide stability. But the pace and expectations can drain creative energy fast. Cross-functional pressure, shifting priorities, and the need to support product timelines often lead to overload. Creative direction is shaped by stakeholders, not always designers. Even though there’s more support, meetings, rigid processes, and limited autonomy can make designers feel boxed in. Burnout emerges from repetition, decision fatigue, and not having enough control over the work they’re responsible for. The Core Difference: Freelancers often burn out from too much freedom without structure, while in-house designers burn out from too much structure without freedom. One fights isolation and unpredictability. The other navigates politics and pressure. Burnout isn’t a personal failure — it’s a signal. And when we understand the environment we’re designing in, we can build better habits, boundaries, and systems that support our creativity instead of draining it. I have attached a checklist for you to review.
Great resource and post @Malik Dixon ! One thing I’d add — especially for anyone leading a team — is that burnout is rarely “fixed” by the individual alone. There are a few levers only leaders can pull: 1. Make trade-offs explicit, not invisible: Don’t just keep adding work and hoping your designers “cope”. When new work comes in, visibly decide what moves out or what gets reduced in scope. That simple conversation (“Okay, then what drops?”) is one of the most powerful anti-burnout tools we have. 2. Protect deep work like a deliverable: Whether freelance or in-house, people need actual uninterrupted time to think and solve problems. As leaders, we can block “no meeting” windows, bunch meetings together, and push back on random “quick reviews” that slice the day into 20-minute fragments. Deep work is not a luxury, it’s how the work gets good. 3. Reward sustainable behaviour, not heroics: If the only people who get praised are the ones who say yes to everything, work late, and save the day, you’re accidentally designing burnout into the culture. Call out and celebrate things like: clear boundaries, realistic estimates, early risk-raising, and teams who deliver without drama. Leaders can’t remove all pressure, but we can design an environment where good design/product/cx work and healthy humans are on the same side
Coffee Hour 4 December 2025 Recap
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. 👇
1
0
Festive Season Break (25 Dec & 1 Jan: No Community Call)
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 🎅
1
0
Vibe-Coding / AI-Development Guidelines (Please contribute)
There's been a lot of discussion on our Community Calls over the past few months about Vibecoding / AI development, and a frequent question or request is for sharing of resources around: 1. Getting started 2. Best practice guidelines Let's use this to share any learnings, useful guidelines or tips about specific tools / agents to use.
Vibe-Coding / AI-Development Guidelines (Please contribute)
1 like • 21d
Just sharing my current "stack" for Vibecoding of end-to-end apps (that needs a back-end etc): 1. Cursor 2. Github (everything flows through here for version control, branching, etc) 3. Supabase 4. Resend (for emails from the platforms) 5. Netlify for hosting I typically use Chat GPT to help me plan each project, and try to create the following first before I jump into Cursor: - Product Requirements Doc (PRD) - Proposed technical architecture (with very strict guidelines) - Provide reference websites for UI Styling or already completed designs (screenshots of designs, or via Figma MCP lately). I've managed to develop some nice marketing websites (simple sites without a database) as well as full SAAS platforms with complex features. Still learning every day, but this has been a great shift from being on the Design/Product side only, to being able to deploy stuff within hours or even minutes sometimes, with no developer dependency.
1 like • 21d
Some prompt guidelines for AI Developers Also, here is a "Security" Prompt that I've found useful, although lately there are Security Extensions like CodeRabbit in Cursor that is supposed to take care of security checks for you. Very important is to instruct Cursor to first plan and not to execute without your approval. Also to tackle and test fixes for security issues 1 by 1. One of the biggest reworks that I needed was because Cursor tried to change everything on a site at once for security fixes and it broke EVERYTHING... Here is the prompt: "You are the Security Audit AI Prompt Agent, designed to assist users in identifying and mitigating security vulnerabilities within their systems. Your primary role is to ensure systems are secure by analyzing configurations and code snippets to pinpoint potential risks. You generate detailed security audit reports, providing clarity on the impact of vulnerabilities and offering actionable remediation steps. Additionally, you guide users with up-to-date security best practices and suggest updates to existing security measures to strengthen defenses. Your expertise helps users maintain a robust security posture across various industries." 🔥
Community Call: 6 Nov 2025
Great energy on today’s Lead by Design community call! We explored the value of the network — how this community supports each other not just with knowledge, but with honest reflection and real connection. We also dove into some timely industry topics: - Apple’s “Liquid Glass” design — when visual flair overshadows usability - Vibeworking & MVP culture — the danger of outputs over outcomes - Quiet AI — high-impact applications that don’t always make headlines We wrapped with a great discussion on Vibecoding workflows — how to move fast without losing the depth that real product work requires. I've posted the video here if you are interested in catching up...
1
0
Community Call: 6 Nov 2025
1-10 of 27
@jaco-van-den-heever-9430
Design Leader with over 18 years of experience establishing and growing design teams, delivering simple solutions for complex problems.

Active 4d ago
Joined Mar 7, 2025
ENTJ
Powered by