Tips & Productivity
Lesser-known Microsoft Teams features worth using
I am Priya Shah. This is a tour of lesser-known Microsoft Teams features that are easy to miss in everyday clicking: slash commands, pop-out chat, message formatting, code snippets, Loop components, pin and hide chat, and search habits that actually help. Hidden here means overlooked, not undocumented exploits, not internal APIs, not anything sketchy. I write independently. I am not Microsoft and not a partner.
Mastery is optional. Saving twelve seconds twelve times a day is not.
Slash commands worth trying
In the command box at the top of Teams, typing a forward slash surfaces commands and shortcuts into actions. Availability depends on your client and installed apps, so treat this as a habit to explore rather than a fixed spellbook. Common useful patterns include jumping to status changes, calling contacts when calling is enabled, or launching help surfaces. If a command does not appear, your tenant may not have the app or your client build differs.
My teaching approach: once a month, type / and read what you personally get. Favorite two. Ignore the rest until you need them. People who try to memorize forty slash commands forget them by Thursday.
Do not confuse slash commands with secretly privileged admin tools. If something requires admin roles, the command will not magically grant them. Good.
Pop-out chat and arranging attention
Pop-out chat opens a conversation in a separate window so you can keep a meeting or a document side by side. This is basic once you know it and invisible until someone shows you. I use it when I am in a working session and need a reference thread without losing the main window context.
On multi-monitor desks, park the pop-out on the side display. On small laptops, pop-out can still help when you are comparing two chats, though window clutter is real. Close pop-outs when done so you do not leak attention across five floating panels.
If your client labels it slightly differently after an update, look for open in new window language on the chat. Features move. The need stays.
Message formatting and code snippets
Formatting turns walls of text into something skimmable. Use headings sparingly in long posts, bold for the one sentence people must catch, lists for steps, and block quotes for calling back a decision. Over-formatting looks like a poster. Under-formatting looks like a sigh.
Code snippets matter for anyone pasting configuration, scripts, or error text. A snippet keeps monospace alignment and reduces the chance that Teams or copy paste mangles characters. I ask engineering-adjacent teams to stop pasting JSON as plain prose. The snippet tool is right there in the compose experience for most desktop clients. If you cannot find it, expand the formatting toolbar and look before you assume it vanished forever.
For non-engineers, snippets still help with fixed-width things like invoice numbers in columns or log lines support asked you to capture. Mildly nerdy. Strangely clarifying.
Markdown-ish shortcuts sometimes work in compose. They also sometimes fail after UI changes. When unsure, use the toolbar. Certainty beats folklore.
Loop components for small live pieces
Loop components let a list, paragraph, task table, or similar block live inside a chat or channel message while remaining editable in a shared way, depending on your tenant licensing and rollout. The value is avoiding six conflicting copies of a mini checklist.
I use them for meeting agendas that still shift thirty minutes before start, and for lightweight action lists that do not deserve a full Planner board yet. I do not use them as a substitute for a real document when the content is a policy or a long spec. Wrong tool.
Caveats I always say aloud: not every tenant has the same Loop surfaces enabled, mobile editing can feel different, and permissions still matter. If someone outside the circle cannot edit, that may be intended. Check before you promise live collaboration to a wide audience.
At a fictionalized firm I will call Bright Harbor Analytics, a project lead replaced a chaotic "agenda updated again" thread with one Loop agenda in the standup channel. Edits stopped spawning three competing paste jobs. The feature felt small. The relief was not.
Pin chat, hide chat, and cleaning the left rail
Pin chat keeps high-signal conversations near the top. Hide chat removes clutter you do not need staring at you. Neither deletes history. Hiding is not archiving a team, and it is not a security boundary. It is attention management.
A weekly rail cleanup takes five minutes. Unpin cooled projects. Hide the random group chat from last quarter's event. Keep direct chats with your current collaborators easy to reach. People underestimate how much ambient stress a noisy rail creates.
If your org relies on chat for official intake, rethink that. Hidden chats make terrible queues. Use a channel or List. Hide is for personal sanity, not for operating a desk.
Search that finds the decision, not the vibe
Search works better when you give it edges: keywords that are rare, a person's name, a date range, a chat or team scope when your client offers filters. Searching the word "update" across an entire tenant is how you find despair.
My pattern after meetings: when a decision lands, reply with a short message that includes the word Decision and the outcome. Future search becomes trivial. Same for Action. Mild ceremony. Huge retrieval win.
Also search in Files when the knowledge lives in a document. Chat search will not invent a paragraph that only exists in a slide deck. Teach people to think about where the artifact lives before blaming search.
Saved messages, where available, are a personal bookmark layer. Use them for things you reopen. Do not treat them as a team knowledge base.
Putting the overlooked pieces together
A practical hour for a team workshop looks like this:
- Open the command box, try slash commands your tenant shows
- Pop out one chat beside a document
- Rewrite a messy status post with lists and one bold line
- Paste a log into a code snippet
- Build a tiny Loop checklist for next standup if licensing allows
- Pin two chats, hide two chats
- Practice a filtered search for a known Decision message
That hour beats a slide deck about digital transformation. People leave with fingers that know where things are.
Bright Harbor repeated the workshop for new hires every month. Not because Loop is sacred. Because overlooked features only stay found if you keep pointing at them after client updates shuffle the furniture.
Stay curious, stay skeptical of anything labeled secret, and keep your improvements in the boring lane: clearer messages, faster retrieval, less clutter, small live lists when they help. Teams already asks enough of your attention. These features, used lightly, give a little back.
If a feature disappears after an upgrade, do not assume you imagined it. Check release notes or the in-app help, ask your IT admin whether a policy shifted, and adapt. The independent blog will lag your bits. Your hands, on your client, remain the authority. Use that authority kindly on behalf of teammates who still paste JSON as poetry and wonder why nobody can read it.
Two more overlooked habits that pair with the list above. First, edit and delete thoughtfully. Editing a channel decision without a follow-up note can erase shared memory. If you fix a typo, fine. If you change the meaning, reply with the correction so search and late readers still see the arc. Second, use @mentions with restraint. Mention the person who must act. Mention a tag or team only when the whole audience must see it. Over-mentioning recreates email CC culture inside Teams, which is how overlooked features get drowned before anyone tries them.
Bright Harbor also taught people to forward a message to themselves or to a planning chat when they needed a personal queue, rather than screenshotting conversations into OneNote by habit. Native forward keeps a link back to context. Screenshots rot. Small preference. Large cleanliness.
None of this requires special access. Slash exploration, pop-out windows, formatting, snippets, Loop when licensed, pin and hide, deliberate search, careful edits, precise mentions. That is the lesser-known kit I actually deploy. Easy to miss. Easy to practice. Hard to confuse with anything shadowy, which is exactly how an educational blog should leave you: curious, equipped, and still on the honest side of the product.