Stop asking where that link is.

When important docs, dashboards, queues, and forms are scattered across Slack, bookmarks, and old messages, give each repeated resource a shared shortcut like sh/handbook, sh/support, or go/roadmap.

One name for the whole team

The shortcut becomes the name people remember, and the destination can change later without retraining everyone.

Built from real questions

Start with the links teammates already ask for in Slack, onboarding, support handoffs, and release work.

Small enough to keep current

Owners, tags, usage counts, and direct routes keep the directory useful without turning it into a heavy intranet.

The link problem is usually a habit problem.

A team may already have the right handbook, roadmap, queue, checklist, and dashboards. The hard part is that everyone remembers a different path to them.

Teamshortcuts gives the repeated links stable names. Instead of searching Slack for the latest thread, a teammate can type the same shortcut every time.

where is the support queue?
use sh/support
sh/support Support queue sh/onboarding New hire checklist go/roadmap Product roadmap

If the same link gets asked for twice, it probably deserves a name. The first useful directory is not a complete catalog; it is a short list of the resources that interrupt work when nobody can find them.

Start with the repeat questions.

Look for the links people request in onboarding, weekly planning, support handoffs, release work, sales calls, and people operations. Those are the resources that create the shortcut habit fastest.

  • sh/handbook for policies, norms, and benefits.
  • sh/onboarding for new-hire setup and first-week resources.
  • sh/deploys for release checklists and rollback notes.
  • sh/support for queues, escalation guides, and customer views.
  • go/roadmap for product plans and planning notes.

Give every shortcut an owner.

A shortcut works because the name stays stable. An owner makes sure the destination stays right when a doc moves, a dashboard changes, or a process gets replaced.

Use aliases only when they match team language.

Teamshortcuts keeps sh/ as the default prefix. Teams can also enable go/, jump/, and to/ as aliases when those words already feel natural.

Make the first workspace useful before inviting everyone.

Add 10 to 20 shortcuts, test the direct routes, then invite teammates. A small directory with the right links beats an empty workspace with a long rollout plan.

How Teamshortcuts helps.

Create a free workspace, add shortcuts with owners and tags, search the directory, and open direct routes for the links your team uses every week. The Team plan adds more members, usage stats, import/export help, and faster setup support.

Related: internal short links, go/ shortcuts for small teams, and internal short links vs bookmarks.

Name the link before it gets asked for again.

Create a Teamshortcuts workspace, add the first repeated resource, and give teammates one name they can remember.

Start free