Skip to main content

OS Toolbox

Track your team's progress mastering the concepts, tools, and disciplines that power your operating system.

Written by Tommy Mains

The OS Toolbox is the Ninety tool your team uses to track how well it has mastered the concepts, tools, and disciplines (CTDs) that make up your Business Operating System. It appears as the Mastery segment in your Quarterly Planning Meeting agenda and as Mastery in Partner Hub, and your company can rename it — some workspaces use a custom name such as "PMI Way." Every team member can view their team's progress; Owners, Admins, and Coaches can confirm mastery and manage the tool's resources.

What the OS Toolbox is

The OS Toolbox shows each part of your operating system as a card your team can mark as mastered over time. Because the tool can be renamed, the same feature shows up under different labels depending on where you are in Ninety:

  • In the Quarterly Planning Meeting agenda, it's the Mastery segment.

  • In Partner Hub and your company's language settings, it's listed as Mastery.

  • In your workspace, it may carry a custom name your company chose (for example, "PMI Way").

Whatever it's labeled, it's the same tool, and it tracks the same thing: how fully your team has adopted its CTDs.

Where to find the OS Toolbox

You can reach the OS Toolbox two ways:

  • Click its name in the left navigation (it may appear as OS Toolbox, Mastery, or your company's custom label).

  • Open it automatically during the Mastery segment of a Quarterly Planning Meeting.

How mastery tracking works

The OS Toolbox presents your operating system as a set of resource cards — such as Assessment, Vision, Goals, Structure, People, Customer, Meetings, Data, Process, and Exit. Each card represents a concept, tool, or discipline your team is working to master.

For each card, your team can:

  • Mark it as Mastered or Not Mastered to reflect where you stand.

  • Click Learn More to open guidance on that concept or tool.

  • Track overall progress at the top of the page, shown as a percentage and a count (for example, "0 out of 12").

Owners, Admins, and Coaches can confirm mastery of a concept or tool, add, edit, archive, or delete resources, edit the toolbox layout, reset resources to the Business Operating System default, and create an Issue or To-Do from any element. Observers cannot manage the tool.

Using the OS Toolbox in a quarterly planning meeting

During the Mastery segment of a Quarterly Planning Meeting, your team reviews the cards in the OS Toolbox and decides where to focus next. The facilitator presents three options:

  • Cascade. Push CTDs the leadership team already uses out to the rest of the organization.

  • Mastery. Deepen how well the team uses the CTDs it already has.

  • Expansion. Add a new CTD to address a new challenge or support growth.

For the full meeting agenda this fits into, see Quarterly Planning Meetings.

Renaming or configuring the OS Toolbox

Because the OS Toolbox is configurable, Owners and Admins can rename the page and its resources from your company's language settings, and coaches and partners can configure it for client templates from Partner Hub.

  • In language settings, you can change the Page Name and the singular and plural Resource labels.

  • In Partner Hub, configure the Mastery tool's options as part of a client template.

Troubleshooting

My agenda says "Mastery," but the page that opens is called "OS Toolbox" or something else.

That's expected. The Mastery segment of the Quarterly Planning Meeting opens the OS Toolbox, and because the tool is renameable, your workspace may display a different label. It's the same tool.


Where is the Mastery tool?

The "Mastery tool" is the OS Toolbox. Look for it in the left navigation under OS Toolbox, Mastery, or your company's custom name, or open it during the Mastery segment of a Quarterly Planning Meeting. If it's missing entirely, an Owner, Admin, or Coach may have disabled it.

Helpful resources

To learn more about mastering your operating system, explore the following:

Did this answer your question?