Side Projects vs. Going Deep:
Which One Grows Your Career Faster?
"Build side projects" and "master your craft" are both standard career advice — and they directly contradict each other. The truth is that one of them is right for you right now, and the other one is probably a distraction. Here's how to figure out which is which, and how to avoid the trap of doing both badly.
Why This Question Is Worth Taking Seriously
Scroll through LinkedIn on a Sunday evening and you'll find two competing religions. One camp posts about their side project — the newsletter they've built, the app they shipped, the consulting client they landed. The other camp posts about the 10,000 hours they've put into their craft, the promotions that came from pure focused excellence, the danger of spreading yourself too thin.
Both camps have people who succeeded doing exactly what they advocate. Both camps also have a silent majority who tried the same approach and burned out, stagnated, or just never got the return they expected.
The problem isn't the advice. The problem is that both pieces of advice are context-dependent — and neither camp tells you what context they're actually speaking from.
The Actual Question to Ask
Not "should I build side projects?" but "what is the specific constraint on my career trajectory right now — and which of these two strategies directly addresses that constraint?" Everything else is noise.
The two career constraints this question is really about:
Constraint A: Credibility Gap
You're not being taken seriously because your depth of expertise isn't yet undeniable. The solution is going deep. More breadth won't fix a credibility problem.
Constraint B: Opportunity Gap
Your current environment doesn't reward your skills — you're capped by budget, industry, or company trajectory. The solution is building portable assets. More depth in a dead end won't open new doors.
The Case for Going Deep
Depth creates scarcity. Scarcity creates leverage. This is the core logic of the "go deep" argument, and it's more durable than it sounds in the age of generalist social media careers.
The professionals who command the highest salaries and the most interesting opportunities are almost always deeply expert in something specific — even if they've eventually built breadth on top of that core. The breadth came later. The depth came first.
💡 What "Going Deep" Actually Looks Like in Practice
Deep isn't just "work longer." It's deliberate practice in the specific sub-skills that distinguish good from great in your field. For a product manager, that might be structured user research methods. For a financial analyst, it might be building fluency in a modeling technique that most peers avoid. For a software engineer, it might be systems design at scale.
Ask yourself: "What's the hardest problem in my field that I can't yet solve confidently?" That's your depth target. Not "what's another certification I could add."
The Case for Side Projects
Side projects get a lot of breathless coverage partly because the success stories are dramatic — the newsletter that became a company, the open-source repo that landed a job at a top-tier employer, the freelance client that turned into a full pivot. The failures don't get written about.
But when side projects work, they tend to solve problems that depth alone can't fix. Specifically: they create proof of capability outside your current context, they build a network independent of your employer, and they generate optionality in a career that might otherwise have a narrow path.
What to Choose by Career Stage
The right answer changes as you move through your career. Here's a stage-by-stage breakdown with an honest assessment of what each phase calls for.
Side Projects That Actually Pay Off
If you've decided a side project is the right move for your situation, these are the principles that separate the ones that generate real return from the ones that absorb time and produce a line on a resume nobody asks about.
It needs a target outcome, not just a topic
"Building a data science portfolio" is a topic. "Getting hired as a data scientist at a mid-size tech company within 12 months" is a target outcome. The project should be designed backward from the outcome. What will a hiring manager or potential client actually look at? Build that. A GitHub repo with five half-finished notebooks doesn't pass the "would this change anyone's hiring decision" test. A single end-to-end project with clean documentation and a real-world dataset probably does.
It should build on existing expertise, not start from zero
The highest-ROI side projects leverage what you already know in a new context — not an entirely new field from scratch. A financial analyst who builds a model-driven investing newsletter is building on existing expertise. The same analyst starting a food blog is starting from zero with no credibility advantage. Where possible, make your side project an extension of your professional value, not an escape from it.
One real project beats five theoretical ones
The most common side project failure mode is parallel exploration — starting multiple things, getting early momentum on each, and finishing none of them. Pick one. Run it far enough to have something real to show: a finished product, a real client, a published piece of work, a measurable result. One completed thing with a clear outcome is worth ten promising starts.
Your primary job performance comes first — always
This sounds obvious but gets violated constantly. A side project that causes your day job performance to slip is not a career accelerant — it's a career risk. You need the income, the reputation, and the reference from your current employer. If your side project is consistently competing with your primary job for your best hours and energy, something has to give. And it should be the side project, not the job.
Check your employment contract before you start
Many employment agreements include clauses about outside work, intellectual property, and non-compete restrictions. In the US, some states limit the enforceability of these clauses — California is notably restrictive on non-competes, for example — but you need to read your actual contract, not assume. Freelancing in the same industry as your employer, or building something that uses work infrastructure or IP, is where conflicts arise. When in doubt, have a quick conversation with HR or an employment lawyer before launching.
Side Project Types: Expected ROI by Goal
| Project Type | Best Career Goal | Time to Meaningful Return | Failure Mode |
|---|---|---|---|
| Portfolio project (code, design, writing) | Job change, industry switch, skill proof | 3–6 months for one strong piece | Multiple unfinished projects; no narrative |
| Freelance / consulting work | Income diversification, transition proof | 2–6 months to first real client | Underselling, scope creep, no positioning |
| Newsletter / content / thought leadership | Network building, external reputation | 12–24 months for meaningful audience | Content treadmill with no clear niche |
| SaaS product / app | Entrepreneurship proof, technical depth | 6–18 months, high variance | Feature creep, launch paralysis |
| Course / workshop / community | Monetize existing expertise, teaching proof | 6–12 months for first revenue | Building before validating demand |
Going Deep That Actually Works
"Going deep" is not the same as "working harder at the same things." Deliberate depth has a structure. Here's what it looks like in practice.
Identify the one sub-skill that separates good from great in your field
This requires talking to people who are excellent at what you're trying to become and asking them directly: "What's the skill that separates the best from the rest in this role?" Their answer is your depth target. It's almost never the thing most training programs emphasize.
Seek work at the edge of your capability, not in the comfort zone of your competence
Deliberate practice (the framework from performance psychology) requires operating at the difficulty level just above your current ability — where you're challenged but not overwhelmed. If your work is consistently comfortable, you're maintaining, not developing. Ask for the harder assignment. Volunteer for the project nobody else wants because it's difficult.
Create feedback loops — don't wait for performance reviews
Depth develops faster with frequent, specific feedback. Ask your manager, peers, and stakeholders for feedback on specific pieces of work — not generic "how am I doing" feedback but "what would make this analysis stronger?" or "what's the weakest part of how I ran that meeting?" The higher the frequency of specific feedback, the faster the improvement curve.
Make your depth visible — it doesn't signal itself
Deep expertise that nobody knows about is a professional asset that's effectively inert. Teach what you know (run a lunch-and-learn, write an internal doc, mentor a junior colleague). Speak up in meetings with the specific knowledge you've built. Connect your depth to business outcomes your company cares about. Depth that surfaces in the right conversations gets noticed; depth that lives in your head only doesn't.
The Trap: Doing Both Badly
The most common outcome isn't choosing depth or breadth — it's choosing neither cleanly and doing both at a level that produces mediocre results in both directions.
This is the split-attention trap, and it's more insidious than it sounds because it can persist for years while feeling like productive busyness. You work on your side project on weekends, you put in the hours at your day job, and neither one gets your sustained best effort. The day job doesn't advance because you're not going deep enough to become undeniably excellent. The side project doesn't get traction because it's not getting enough consistent effort to build real momentum.
Signs You're in the Split-Attention Trap
You've had the same side project "in progress" for more than 12 months without a concrete output.
Your day job performance reviews are "meets expectations" — not outstanding — and have been for 2+ years.
You feel busy all the time but can't point to meaningful career progress in either direction.
You're running two or more side projects simultaneously, none past early stages.
Your side project is providing entertainment and the feeling of progress, but you could articulate no clear career outcome from it succeeding.
The way out of the trap is a simple decision: for the next 90 days, which one gets your focused effort — the day job or the side project? Not 70/30. Pick one to go all-in on and deprioritize the other. Revisit in 90 days.
💡 The 90-Day Rule
Most things in your career look different after 90 days of focused effort than they do after 90 days of half-effort. This applies to both depth (consistent focused practice will visibly improve your performance) and breadth (a focused 90-day sprint on a side project will tell you whether it has real traction or whether it's a hobby). Use 90-day periods as your unit of focused investment — then reassess.
More in the Career Development Series
B-3-P · Pillar
The Working Professional's Development Playbook
The full framework: the three-layer model, career stages, and how to build your annual plan.
B-3-C1
Which Certifications Actually Move the Salary Needle
If you're going deep, here's which credentials actually validate and accelerate that investment.
B-3-C2
Business English That Matters
Whether you're going deep or pivoting, communication is the meta-skill that amplifies everything else.
B-4-P · Career Transition
The Complete Guide to Career Transitions (2026)
If your side project is building toward a full pivot, here's how to make that transition cleanly.
B-3-H1 · How-To
Building Your Annual Development Plan
Once you've decided your direction, build the plan that makes it happen — step by step.
FAQ
I genuinely don't know whether I've hit my ceiling at my current company or just hit a plateau. How do I tell the difference? +
Ask your manager directly: "What would need to be true for me to reach [next level] in the next 12–18 months?" If the answer is specific and achievable ("you need to lead a cross-functional project and demonstrate X"), you haven't hit the ceiling — you're on a plateau with a visible path up. If the answer is vague ("it's about budget," "the org isn't structured for that right now," "we'll see"), or if the honest answer is that the role doesn't go higher, you've found the ceiling. The direct conversation is the fastest diagnostic.
My side project is making more money than I expected. When should I consider making it my main thing? +
The decision is usually not about revenue alone — it's about trajectory and risk tolerance. A common rule of thumb: when your side project is generating 50–75% of your current salary consistently (not one good month) and has shown growth for at least two or three quarters, the conversation about full transition becomes financially rational. Before that, the question is whether your current job is actively limiting the side project's growth or whether you can continue doing both. Most people transition too early. The financial runway math matters: three to six months of living expenses in reserve before you leave employment is the minimum, not the goal.
I'm in a field (finance, law, medicine) where depth seems like the only acceptable path. Is breadth ever relevant here? +
Yes — but breadth in these fields looks different. It's not side projects in the conventional sense; it's cross-functional depth. A lawyer who also has deep business fluency has a real advantage over one who doesn't. A doctor who understands healthcare administration and policy is more effective in leadership roles. A finance professional who understands the operational reality of the businesses they're financing makes better decisions. The breadth that works in credential-heavy fields is adjacent expertise that enhances the primary discipline, not divergence from it.
What's the most common mistake people make with side projects? +
Building before validating. The energy of a new idea is highest at the start, and most people pour that energy into building — the product, the website, the course content — before they've confirmed anyone wants what they're building. The professionals who get side projects off the ground fastest start by finding one real potential customer or audience member and asking them to pay for or engage with something minimal. If you can't get a single person interested enough to give you money, time, or an email address before you've built anything, you don't have a product problem — you have a validation problem. Solve the validation problem first.
I'm worried about burnout. How do I pursue either path without destroying my work-life balance? +
The burnout risk is real and worth taking seriously. The honest answer: unsustainable intensity is always time-limited. A 90-day focused sprint on either path is manageable; two years of relentless dual-track effort is not. The key is building in explicit recovery periods — after a focused sprint, ease off deliberately before starting the next one. The other protective factor is energy source: if your side project genuinely energizes you rather than depleting you, it's sustainable longer. If it feels like a second job that you resent by Sunday evening, that's information about fit, not just discipline. The right side project for the right person can actually reduce burnout by creating a sense of agency and progress that a frustrating day job suppresses.
The Decision Framework · Summary
How to Make the Call
Diagnose the constraint first. Is your career limited by a credibility gap (go deep) or an opportunity gap (build breadth)? These require different solutions.
Know your career stage. Early career defaults to depth. Mid-career requires honest diagnosis. Senior career shifts toward strategic breadth built on established depth.
If you go the side project route: one project, clear outcome, built on existing expertise, primary job protected.
If you go the depth route: target the specific sub-skill that separates good from great, seek work at the edge of your capability, and make your expertise visible.
Avoid the split-attention trap. Doing both half-heartedly produces mediocre results in both directions. Commit to one for 90 days, then reassess.
The professionals who grow fastest aren't the ones who do the most. They're the ones who correctly identify which lever moves their specific situation — and pull it hard.