Workflow Automation
Reducing manual work with Microsoft Teams automation
I am Priya Shah. Reducing manual work in Microsoft Teams is less about hunting exotic connectors and more about watching what people click every week, then replacing three painful loops with something boring and reliable. This is an independent field note, not a Microsoft pitch and not a partner playbook.
If your automation plan starts with a forty-box architecture diagram, pause. Start with a notepad and a Tuesday.
Audit a week of repeated clicks
I ask teams to keep a crude click diary for five workdays. Not a productivity cult spreadsheet. A note each time they do the same dance twice. Copying chat text into a tracker. Downloading a spreadsheet someone posted, editing it, uploading it again. Asking the same three questions in intake. Rebuilding a weekly status message by hand. Forwarding the same announcement into six channels because nobody knows which team owns the audience.
At Northvale Paper Co., a mid-size packaging firm with a chatty Teams tenant, I sat with operations for one week in March. The diary looked almost silly. Every morning Maya pasted yesterday's open orders from an email into a channel message. Every afternoon Jordan downloaded a shared Excel from Files, filtered to his plant, and typed counts into a different chat. Twice a day someone asked "who owns shift swap approvals" and got three different answers.
None of that required artificial intelligence. It required admitting the clicks were the product.
Rules for the diary:
- Write the trigger, the steps, roughly how long, and how often
- Ignore one-off chaos unless it is a monthly monster
- Capture who gets interrupted, not only who clicks
- Note where people leave Teams to finish the job in email or a personal notebook
At the end of the week, sort by frequency times minutes. The top of that list is your backlog. Ego projects that "feel strategic" go below anything that burns thirty minutes daily for three people.
Pick three flows, not thirteen
Ambition kills adoption. I force a shortlist of three. At Northvale we chose:
- Morning open-orders digest posted automatically from the system export into one operations channel
- Plant counts collected through a Form that writes to a List, with a daily summary message
- Shift swap requests routed through a List with an approval and a clear owner channel
Everything else waited. The weekly all-hands reminder. The visitor badge form. The nice-to-have dashboard. Waiting felt rude to the people who wanted a revolution. It saved the rollout.
Selection criteria I use: the work already has a stable trigger, the data has a home that is not a private inbox, and failure is recoverable. If the source system cannot export reliably, fix that first. Automating a broken feed creates beautiful wrong messages.
Also ask who will own the flow when the builder goes on leave. If the answer is a shrug, you do not have three flows. You have three future outages.
Measure time in a plain way
I distrust fancy ROI calculators that invent hours saved to twelve decimal places. Measure like a shop floor.
Before change: time five real runs of the manual path. Write the median. After change: time five real runs of the new path, including the awkward first week. Compare medians. Add a note about interruptions removed, because Maya no longer pings Jordan for the plant filter.
Northvale numbers, rough and honest:
- Morning digest: was about 18 minutes of copy paste and formatting, became about 2 minutes of glance and pin
- Plant counts: was about 25 minutes across people, became about 8 minutes of Form entry plus a generated summary
- Shift swaps: was a 40 minute scavenger hunt across chats, became a 10 minute Form and approval with a visible status
Those are not income promises. They are minutes returned to people who still had plenty of other work. We wrote them on a OneNote page titled "what changed" and revisited after thirty days. Two numbers got worse for a week while people learned the Form. We kept the Form anyway because the second week recovered and the audit trail appeared for free.
If leadership wants a slide, give them medians and a sentence about fewer "did you see my message" chases. Skip theatrical annualization unless they already demand it, and even then keep the math boring.
Design the replacement so bypass is annoying
People bypass flows when the old path is easier. So make the new path the path of least resistance, and make the old path politely useless.
For Northvale's plant counts, we stopped accepting typed numbers in chat as official. Jordan still could type them. Maya would reply with the Form link and not update the List from chat improvisation. One week of gentle refusal trained the habit better than a policy PDF.
For shift swaps, managers agreed they would only approve items in the List. Side DMs still happened socially. The schedule of record only moved after the List status flipped. That distinction matters. You cannot ban human conversation. You can refuse to treat conversation as the system of record.
Channel hygiene helps. Put the Form link in the channel description, pin a how-to message, add a tab if useful. If the link is three folders deep in SharePoint, people will invent a shortcut through Maya.
Change management that is not a pep rally
Announce the change once with a short demo recording. Name the go-live date. Name the owner. Show the before path and the after path in under five minutes. Then hold office hours for two mornings. Then stop selling and start operating.
Watch for shadow work. If someone builds a parallel Excel because they distrust the List, address the distrust. Sometimes the List view is ugly. Fix the view. Sometimes they need a column you forgot. Add it. Sometimes they simply hate change. Keep the boundary anyway, kindly.
Retire the old ritual explicitly. "We will no longer post morning open orders by hand starting Monday." Ambiguous sunsets keep both paths alive forever, which doubles work instead of reducing it.
I also ask teams to nominate a bypass watcher for the first fortnight. Not a hall monitor with a clipboard. Just someone who notices when chat becomes the old spreadsheet again and redirects without drama.
What broke, and what we kept
Northvale's first digest failed because the export filename changed on Thursdays. Classic. The flow looked for OpenOrders.csv and got OpenOrders_Thursday.csv. We widened the trigger to the folder and sorted by modified time. Document that kind of brittleness in the flow description so the next owner is not surprised.
The shift swap Form originally allowed free text for the covering person. People typed nicknames. Approvals stalled. We switched to a person field. Adoption dipped for a day, then rose.
We did not automate the all-hands reminder in that phase. Someone still posts it. That is fine. Manual work that happens once a week and takes four minutes is not a crisis. Manual work that happens twice a day and creates arguments is.
A reusable checklist for the next team
When I leave a team with this pattern, I leave a checklist, not a myth:
- Diary one week of repeated clicks
- Rank by frequency times minutes
- Pick three flows with clear owners
- Time five runs before and five after
- Make the system of record obvious
- Refuse unofficial updates without being cruel
- Retire the old ritual on a named date
- Review numbers at thirty days and drop what did not help
Teams is the place people already argue and coordinate. Use it as the notification and conversation layer. Keep structured work in Lists and Forms. Let automation move facts, not personalities.
Northvale still has messy chats. Of course they do. They also have three boring lanes that no longer depend on Maya's morning stamina. That is the kind of reduction I will defend in any room. Small. Measured. Owned. Hard to bypass without looking intentional. And intentional bypass is rarer than accidental drift, once the easy path points the right way.
If you try this next month, resist adding a fourth flow mid-week because someone important had a sparkly idea. Capture the idea on a parking list. Finish the three. Measure. Then negotiate. The discipline is the automation.
What I look at on day thirty
Thirty days is long enough for the novelty to wear off and short enough that people still remember the old path. I pull the audit list, the run history, and a five-line note from the owner. I want three numbers: how many times the flow ran, how many of those runs a human had to repair, and whether the diary clicks from week one actually disappeared.
If repairs are common, the flow is not saving time. It is relocating the busywork onto whoever watches the failures. I would rather delete it than leave a red badge in Power Automate that everyone learns to ignore. Northvale dropped an early version of the digest for that reason, then brought it back once the filename problem was boring and documented.
I also ask one person who does not own the flow whether they trust it. If they still keep a private copy of the list, the system of record is not real yet. Fix that before you automate a fourth thing. The win is a quieter morning, not a larger catalog of flows.