Build an app store for how your team works

Your team has the tools. What it doesn't have is a shared way of using them, and that's the whole problem.

Everyone runs their own improvised version of the work, so you end up with ten people pulling in ten directions and a company that somehow moves slower the more it adds.

Think of it as vectors. When everyone's arrow points a different way, the forces cancel and you go nowhere. Line those arrows up and the same headcount suddenly covers ground.

The tool that lines them up isn't a tool at all. It's a skills repo.

Here's how to build one that people actually open:

Start with the skill itself

A skill is just a process you've figured out, written down so cleanly that someone else can run it without you in the room. Some teams keep these as a simple skills.md file.

You take the thing you know how to do, the lead dossier you build, the cold outbound sequence you've tuned, and you hand it off as a file. The next person injects it and instantly inherits the work you already perfected. No shadowing. No month of "let me show you how I do it." They just get infused with the skill and go.

That's the unit. But where do you keep them?

Build the repo like an app store

Don't think of a folder. Think of Apple's App Store.

A searchable place where every skill lives, nothing gets deleted, and the best ones rise on their own. Add upvotes so usage sorts the list for you. The skills people actually run climb to the top, the dead ones sink, and you never have to play librarian.

You can even make them forkable too. Someone grabs your outbound skill, tweaks it for their accounts, and maybe that fork turns out sharper than the original.

Now it spreads. One person's improvement becomes everyone's default, and the whole library gets better without a single meeting about it.

Wire it into onboarding by role

This is the biggest danger. The skills exists, it's sitting right there, but a new hire opens it on day one and sees a wall of skills with no idea which ones are actually theirs. So they close the tab and go ask a person instead, which is the exact thing the repo was supposed to replace.

The fix is to route people the moment they walk in. Someone joins on the sales side, so you hand them the lead dossier builder and the outbound optimizer and nothing else yet. Account management gets the onboarding sequence. Paid media gets the ad conversion ops skill.

Everybody's drinking from the same source of truth, they're just each handed the part that matters for the job they're actually doing. Do that and a new hire is shipping real work in a few days instead of spending a quarter figuring out where things live.

And once they've found their footing, let them start adding their own skills to the pile. That's the part that makes it last. The repo stops being something leadership maintains and becomes something the whole team is building out from the edges, a little better every week.

Measure it so it stays alive

A repo that nobody adds to is just a graveyard with better search. So you have to watch it the way you'd watch any other living thing in your company, which means actually tracking what's happening inside it.

Look at participation by team, so you can see which groups have bought in and which ones are quietly ignoring the whole thing. Look at completions, contributors, runs by team. Put up an individual leaderboard so the people doing the work get seen doing it.

Then take all that and turn it into a game, in whatever shape fits your culture. The moment a skill climbing the leaderboard earns someone a little real recognition, contributing stops feeling like a chore you nag people about and starts feeling like something they want to be caught doing.

That's the flywheel.

People build, the good stuff rises, the recognition pulls in more building, and the whole library gets richer on its own without you standing over it.

Why this is the unlock

Stack three more tools this quarter and you'll feel busier and ship less.

Build one repo where your best work lives, spreads, and sorts itself, and every arrow on the team starts pointing the same way.

If you want the full breakdown, watch this: https://www.youtube.com/watch?v=cP7QQsBQ1zg

To building a smarter team,

Eric Siu