A skill one person has is half a skill
The contract-review skill from lesson one is genuinely useful to the manager who built it. But if it lives only on her account, the team problem from the start of this chapter is only half-solved.
Picture it. She has a great vendor-contract-review skill. Her six
paralegals don't. So contracts she reviews are consistent, and
contracts the other six review are still done six different ways. The
playbook exists, but it's not deployed. A skill that one person has is
a personal productivity tool. A skill the team has is a standard.
This lesson is about closing that gap: getting a skill from one person's account into the hands of everyone who needs it. There are three ways that happens, and they differ by who's in control.
- Admin provisioning. An administrator pushes a skill to everyone in the organization at once. Top-down, for skills the whole company should have.
- Sharing with colleagues. One person sends a skill directly to specific coworkers. Person-to-person, for a small group.
- The organization directory. Someone publishes a skill to an internal directory where any coworker can find it and install it themselves. Opt-in, for skills worth offering broadly.
The next two steps walk through these. The thing to notice across all three: a skill becomes a team asset on purpose, through a deliberate step. It doesn't spread on its own, and that is exactly what makes the governance later in this chapter possible.
A skill one person has is half a skill
The contract-review skill from lesson one is genuinely useful to the manager who built it. But if it lives only on her account, the team problem from the start of this chapter is only half-solved.
Picture it. She has a great vendor-contract-review skill. Her six
paralegals don't. So contracts she reviews are consistent, and
contracts the other six review are still done six different ways. The
playbook exists, but it's not deployed. A skill that one person has is
a personal productivity tool. A skill the team has is a standard.
This lesson is about closing that gap: getting a skill from one person's account into the hands of everyone who needs it. There are three ways that happens, and they differ by who's in control.
- Admin provisioning. An administrator pushes a skill to everyone in the organization at once. Top-down, for skills the whole company should have.
- Sharing with colleagues. One person sends a skill directly to specific coworkers. Person-to-person, for a small group.
- The organization directory. Someone publishes a skill to an internal directory where any coworker can find it and install it themselves. Opt-in, for skills worth offering broadly.
The next two steps walk through these. The thing to notice across all three: a skill becomes a team asset on purpose, through a deliberate step. It doesn't spread on its own, and that is exactly what makes the governance later in this chapter possible.