What Working at Salesforce Taught Me About Scaling Myself

The Tableau Marketing Engineering Playbook

Three scaling strategies I now swear by:

Documentation as Force Multiplier: My onboarding.md has saved 37+ engineer-hours. It started as a personal “reminder log” and became the most cloned doc on our internal Confluence. I included things like how to run tests, edge case notes, known quirks of our GA integration, and even Slack etiquette. Now, new hires ping me to say, “That doc saved me two days.”
The 30% Rule: Spend 30% of sprint capacity on tech debt—or pay 300% later. I’ve lived both sides. At one point, we deferred one too many refactors and ended up rebuilding a component mid-quarter while trying to ship two campaigns. Chaos. Now, tech debt is budgeted like a utility bill—non-negotiable.
PR Templates: Standardized formats cut review time by 40%. I added sections for context, test cases, screenshots, and rollback plans. It felt silly at first, but it eliminated 80% of the “can you explain this?” comments. And reviewers now leave comments like, “Nice context. LGTM.” Which is basically love in PR language.

Before/After Salesforce

Metric	Pre-Salesforce	Now
Code Reviews/Day	1-2	8-10 (with higher quality)
Meeting Efficiency	"Let's discuss"	Pre-circulated Loom videos
Reusability of Components	"Copy/paste with tweaks"	Published as internal packages

Team Impact as a Metric

I used to measure my productivity by commits and tickets closed. Now I track something fuzzier but more powerful: how many people I’ve unblocked, how often my solutions get reused, and whether the team runs smoother when I’m not around. That last one used to scare me. Now I see it as the goal.

One month, I took a staycation and came back to find teammates had used my docs, scripts, and templates to deploy three updates. I had a mini identity crisis—was I still needed? The answer, of course, was yes. But in a different way. Less keyboard hero. More systems gardener.

"At scale, your keyboard skills matter less than your ability to make others 10% better. I measure my impact in GitHub forks now."

How I Think About Scaling Now

Scaling yourself isn’t just delegation. It’s clarity, context, and removing friction for others. It’s asking “Will this break if I disappear for a week?” and building accordingly. That might mean writing better internal docs. Or automating a routine process. Or creating a team glossary because nobody knows what 'chassis' means anymore.

I’ve also learned to give context upfront—in PRs, Jira tickets, Slack threads—so teammates don’t have to dig. I think of it like future-proofing empathy. If someone’s having a rough week, can my message help them without draining more energy? Can they say “ah, got it” without needing to call a meeting? That’s the bar.

What Scaling Myself Didn’t Mean

Working more hours: In fact, I started protecting deep work time more aggressively.
Becoming a manager: Scaling doesn’t require a title change. Influence is scale.
Automating everything: Some things (like onboarding coffee chats) are better human.

Little Systems, Big Impact

Here are a few micro-systems I’ve set up that made a disproportionate difference:

A one-click script that sets up local dev for our GA4 pipeline. Saved at least five onboarding sessions.
A Slack alias @ga4-help that routes questions to a rotating support dev. No more silent suffering or Slack DMs at 11pm.
A calendar block called "Maker Mornings"—three no-meeting hours daily. I evangelized it, now half the team does it.

Lessons & Reflections

If it’s painful now, someone else will feel it worse later. Fix it early, or document it honestly.
You don’t scale by doing more. You scale by enabling more.
Good systems are invisible when they work and unforgettable when they don’t.

This post offered an unexpected lens into the topic of "What Working at Salesforce Taught Me About Scaling Myself"—something I initially underestimated. What began as a routine story evolved into a surprisingly personal audit of where I’ve grown, where I’ve slipped, and what continues to challenge me. I realized that my path hasn't been about linear progress; it’s been a series of weird detours, punchline errors, and the occasional small win that gave me just enough momentum to keep going.

If there's a takeaway, it’s this: context matters. The same challenge that might’ve broken me five years ago now feels like a teachable moment. And maybe that’s the definition of growth. Thanks for sticking with the post—I hope your own journey is full of equally ridiculous, humbling, and surprisingly meaningful moments.