Microsoft 365 task system rollout for a 17-person operations team

The problem

The owner kept his to-do list in a personal Trello inbox. The office manager re-keyed items into Planner or forwarded them by email. Field and maintenance work was not being delegated at all, because half the crew would never open a task app. Nobody could see what was overdue across departments, and “proof it got done” lived in text messages.

What I did

• Audited the live tenant, the existing Planner exports and the licence mix before proposing anything, so the recommendations came with findings rather than questions.
• Designed the department structure: ten proposed groups consolidated to eight Teams-backed plans, with the merges decided by who actually hands work to whom and who is allowed to see what.
• Built a single Intake plan the owner can post to from his phone, with a routing pass that moves each task to the right department plan with dates and attachments intact.
• Wrote a Task Standard the whole company works to: how a task is titled, what “done” means, and a “proof attached” checklist item on every template.
• Specified Power Automate flows for the next phase: weekly task lists emailed to supervisors whose crews never log in, a proof-of-completion check that reopens tasks closed without an attachment, and a weekly summary for the owner.
• Ran the whole engagement asynchronously: a Loom walkthrough and written update every week, decisions requested in writing with a by-when date, and two-week phases each ending in something the client could open and use.

Outcome

Phase one shipped on schedule with a baseline so the client can measure the change at 30 and 90 days. The owner’s task backlog now lives on a board the whole office can see instead of in one person’s head, and maintenance work is being assigned to the field team for the first time. The client kept me on for the next phase.