Productivity Workflows

If you do the same sequence of clicks every day, you can automate it. Power Automate is the tool — and the threshold for ‘worth automating’ is lower than you think.

If you copy data from one place to another, send the same kind of email regularly, save attachments to a folder, or notify the same people about the same kind of event — you’re doing work a computer should be doing. Power Automate is the Microsoft 365 tool for exactly this. It connects apps and services with a trigger and a series of actions: when X happens, do Y, then Z. Once set up, the flow runs in the background while you do something else.

The mental shift takes a moment. Most people see a repetitive task and accept it as ‘just part of the job’. The instinct that changes things is asking ‘could a computer do this?’. The answer is yes far more often than people realise — and the cost of building a flow is usually 15 minutes for a task that consumed 30 minutes a week. Across a year, that’s 25 hours saved for 15 minutes of setup.

Power Automate has a vast template library for common scenarios — save email attachments to OneDrive, post Teams notifications when something changes, route approvals, send reminders. Start with templates that match your task, customise from there. You don’t need to be technical; the visual builder makes it accessible. Where it gets complex is when you go beyond simple flows into conditional logic, error handling, and multi-step processes — but for most useful flows, basic is enough.

Why this matters

Automation isn’t about being fancy — it’s about reclaiming your attention:

The cost compounds. 15 minutes of automation today saves 15-20 hours over a year. Repeat across 3-4 flows and you’ve built back a working week.

Automated tasks happen consistently. Manual tasks get skipped when you’re busy. Flows run regardless of your schedule, your mood, or your meetings.

Automation removes the small frictions. Each repetitive task carries a small mental cost; eliminating them adds up to clearer thinking on the stuff that matters.

When you’ll use this

• When you’re doing the same multi-step task every day or week.
• When data needs to move between apps regularly (email → file storage, form → Teams, etc.).
• When notifications need to be sent based on triggers you can identify.
• When your manual process is reliable enough that an automation could replicate it.

How to do it

1. Identify the task: what’s the trigger, what are the actions?
2. Open Power Automate via the App launcher.
3. Browse Templates for similar scenarios.
4. Pick a template close to your need, or start from blank.
5. Configure the trigger (e.g. ‘When a new email arrives’ or ‘When a file is added’).
6. Add actions step by step (save attachment, send Teams message, update a list).
7. Test the flow with a real example.
8. Turn it on and let it run.

Best practices

• Start with one simple flow. Get it working before building more.
• Use templates as starting points. Don’t build from scratch when something close exists.
• Test before going live. A buggy flow that runs every hour amplifies the bug.
• Document what your flows do. Future you (or a colleague) needs to know.
• Review flows quarterly. Triggers change; flows need maintenance.

Common mistakes

• Trying to automate everything at once. Half-broken flows; lost trust in the system.
• No testing before go-live. Buggy flows multiply problems.
• Cryptic flow names. ‘Flow 1’, ‘Flow 2’ — useless when something breaks.
• Letting flows run for years without review. Triggers and dependencies drift.

↑ Back to top ↑ Back to list

When something needs sign-off, an approval workflow does it cleanly — request, review, decision, audit trail. No more chasing email replies that may or may not count as approvals.

Approvals are one of the most common workflow needs in any organisation: leave requests, document approvals, expense claims, purchase orders, content sign-off. Done by email, they’re a mess — vague responses, lost threads, no audit trail, no idea who’s outstanding. Done with Power Automate’s Approvals feature, they’re clean: structured request, named approver, clear decision, automatic record. The shift is dramatic.

The mechanic is straightforward. Build a flow with an Approval action: define who’s approving, what they’re approving, and how. The approver gets a notification (Teams, email, or the Approvals app), they click Approve or Reject directly from the notification with optional comments, and the flow continues based on the decision. The whole exchange is captured in a record with timestamps.

What this enables is more than process improvement — it’s culture change. Approvals stop being political (who chases hardest, who shouts loudest) and become predictable. Time-to-decision shortens. Audit trails are automatic. Approvers get fewer ‘please approve this’ emails because the system handles routing. For any organisation that does approvals at any volume, formalising them in workflow is one of the highest-leverage moves.

When you’ll use this

• When something needs formal sign-off before proceeding.
• When approvals are getting lost in email threads.
• When you need an audit trail showing who approved what and when.
• When approvers want to spend less time on routine sign-offs.

How to do it

1. Open Power Automate and click Create.
2. Choose the trigger that starts the approval (form submission, file upload, button click).
3. Add the Start and wait for an approval action.
4. Configure: approver(s), title, details, deadline.
5. Add post-approval actions: notify requester, move file, update list.
6. Add post-rejection actions: notify with reason, return to requester.
7. Test with a real approval scenario.
8. Turn the flow on.

Best practices

• Keep approver lists small. 1-2 people per approval, not committees.
• Set deadlines. Approvals that sit indefinitely defeat the purpose.
• Notify in Teams, not just email. Approvers respond faster.
• Capture rejection reasons. ‘Rejected because…’ is more useful than just ‘Rejected’.
• Plan for absences. What happens when the approver is on leave?

Common mistakes

• Five-approver chains. Slow, ambiguous, demotivating.
• No deadline. Approvals stall indefinitely.
• No fallback for absent approvers. Whole flow breaks when someone’s on leave.
• Building elaborate flows when built-in approval would do. Match complexity to need.

↑ Back to top ↑ Back to list

A shared task list makes work visible, accountable, and prioritisable. The right tool depends on the team — Planner, Lists, or To Do — but having one is non-negotiable.

Most team work is held together by undocumented commitments: ‘I’ll send the report by Friday’, ‘I’ll check with Legal’, ‘I’ll update the deck’. Each commitment is fine; the aggregate is fragile. Tasks slip because no one’s tracking. Tasks duplicate because no one knows what’s already underway. Tasks get re-asked because they were never recorded. A shared task list fixes this — making the team’s work visible, accountable, and prioritisable.

Microsoft 365 has three good options. Planner is the team task board — buckets, cards, due dates, assignments, visual at a glance. Best for project teams. Lists is the structured tracker — rows, columns, metadata, views. Best for workflows that need more structure than cards (intake forms, ticket queues, request logs). To Do is personal but integrates with Planner — your assigned tasks across all Plans show up in one place.

The key is to pick one and use it consistently. The team that has Planner for some tasks, Lists for others, and email for the rest is the team that ends up tracking nothing. Pick a primary tool, agree the workflow, train everyone. Within 2-3 weeks, the new system becomes habit and the old chaos fades. The discipline is choosing — not optimising forever between options.

When you’ll use this

• When the team has more committed tasks than can be tracked in heads.
• When tasks are slipping and accountability is unclear.
• When you need visibility across what everyone’s working on.
• When you’re moving away from emails-and-spreadsheets task tracking.

How to do it

1. Decide the right tool: Planner (visual, project-based), Lists (structured, workflow), or To Do (personal).
2. Create the new Plan or List in your Team or Site.
3. Set up the structure (buckets in Planner; columns in Lists).
4. Add the team’s existing tasks.
5. Train the team on the workflow.
6. Make it part of your team’s rhythm (standup reviews the board, etc.).
7. Review and adjust the structure after 2-3 weeks of use.

Best practices

• One tool for the team, not three. Consistency beats sophistication.
• Make it part of meetings. Standups review the board; planning updates it.
• Keep statuses simple. Not started / In progress / Done / Blocked covers most needs.
• Assign owners explicitly. Tasks without owners don’t get done.

Common mistakes

• Multiple competing task tools. Team tracks nothing because they’re in three systems.
• Setting up a board nobody uses. Without team adoption, it’s just storage.
• No status discipline. Tasks marked ‘In progress’ for months.

↑ Back to top ↑ Back to list

Microsoft Lists turns structured tracking into a proper system — better than Excel for trackers, better than Planner for workflows, better than email for ticket queues.

Microsoft Lists is the modern way to track structured information across a team. Think of it as a database designed for non-technical users: columns with types (Choice, Person, Date, Number), views, filters, conditional formatting, automation hooks. The interface is friendlier than a SharePoint list and more capable than a shared Excel sheet. For trackers, registers, ticket queues, intake forms, and ongoing logs, Lists is usually the right tool.

Setting one up is easy. Pick a template (Issue Tracker, Asset Manager, Recruitment, Travel Requests) or start blank. Add columns for the data you need to track. Configure views (group by status, filter to my items, sort by priority). Share with the team. The list lives in SharePoint behind the scenes, with all the governance (permissions, audit trail, retention) that comes with it — but it presents as a clean, modern app.

Where Lists shines compared to Excel: concurrent editing without version conflicts, structured data types that prevent typos, conditional formatting, integration with Power Automate for triggers and notifications. Where it shines compared to Planner: proper column types, multiple views, more structured workflows. Match the tool to the job — Planner for visual project boards, Lists for structured trackers.

When you’ll use this

• When you have ongoing structured data the team needs to maintain together.
• When you’ve outgrown a shared Excel spreadsheet (concurrent editing, version conflicts).
• When you need a tracker, register, intake form, or ticket queue.
• When data needs to trigger automation (Power Automate flows).

How to do it

1. Open Microsoft Lists via the App launcher.
2. Click + New list.
3. Choose a template close to your need, or start blank.
4. Define columns for the data: Choice, Person, Date, Number, Yes/No, etc.
5. Add a few sample rows to test the structure.
6. Configure views: filtered by status, grouped by category, etc.
7. Share the list with the team and set permissions.
8. Add Power Automate triggers if you need automation.

Best practices

• Use proper column types. Choice for categories, Date for dates, Person for ownership.
• Build useful views. Default + ‘My items’ + ‘Recent’ covers most needs.
• Use conditional formatting for visual clarity. Red for blocked, green for done.
• Combine with Power Automate. Trigger notifications, create approvals, sync data.

Common mistakes

• Storing list data in Excel because ‘we always have’. Excel breaks at scale; Lists doesn’t.
• Free-text columns where Choice would work. Inconsistent data, broken filters.
• No views beyond the default. Everyone scrolls through everything.

↑ Back to top ↑ Back to list

Assigning a task with a clear owner and due date is the single most important step. Tasks without owners don’t get done; tasks without dates drift forever.

Every task needs three things to be real: a clear description (what), a named owner (who), and a due date (when). Miss any of the three and the task degrades. ‘We should improve customer onboarding’ is a wish, not a task. ‘Sarah will draft a customer onboarding plan by Friday’ is a task. The structure forces accountability and creates the conditions for the work to actually happen.

In Planner: open a card, set the due date, assign to a team member. In Lists: use a Person column for owner and a Date column for due date. In To Do: assign yourself, add a date. In meeting notes: capture as ‘Action: [person] to [verb] by [date]’. The tool varies; the structure doesn’t — what / who / when, every time.

Where this falls down is in the small assumptions. ‘I’ll send it’ (when?). ‘We need to decide on this’ (who decides?). ‘Let’s revisit this next week’ (next Tuesday? next Friday?). Vague assignments produce vague outcomes. The discipline is to pin down the specifics in the moment — not after, when memory has faded and ‘we agreed Sarah would do it’ becomes a debate.

When you’ll use this

• When you’re capturing actions from a meeting.
• When you’re populating a team task board.
• When delegating work to a colleague.
• When committing to your own work and want it tracked formally.

How to do it

1. State the task clearly: what specific outcome is needed?
2. Assign one named owner (not ‘the team’, not ‘someone’).
3. Set a specific due date (not ‘soon’, not ‘next week’).
4. Add context: what does ‘done’ look like?
5. Confirm the owner has accepted the task.
6. Track it in the team’s task system.
7. Follow up before the deadline if needed.

Best practices

• One owner per task. Multiple owners = no owner.
• Specific due dates. Friday is better than ‘next week’.
• Verb-based descriptions. ‘Draft’, ‘review’, ‘decide’ — clear ownership of the verb.
• Confirm acceptance. ‘Are you good to take this?’ beats assuming.

Common mistakes

• ‘Someone needs to do X.’ No one will. Name a person.
• Vague dates. ‘Soon’ is not a deadline.
• Tasks without context. The owner isn’t sure what ‘done’ looks like.
• No follow-through. Tasks assigned in meetings, never tracked, never delivered.

↑ Back to top ↑ Back to list

Microsoft Forms turns scattered email replies into structured data. For surveys, intake, registrations, or feedback, it’s almost always better than asking people to email you.

Whenever you need to collect the same information from multiple people — registrations, feedback, requests, surveys — Microsoft Forms is the right tool. You build a form with the fields you need, send people a link, and responses arrive as structured data you can analyse, export to Excel, or trigger automation from. Compared to ‘just email me your details’, it’s faster for everyone, more accurate, and produces data you can actually use.

Form fields support the structure you need: short answer text, long answer, choice (single or multiple), rating, date, file upload (in some scenarios). Branching logic means you can show different questions based on earlier answers. The form lives at a unique URL you can share via email, Teams, or embedded in a SharePoint page. Recipients don’t need to be in your tenant — Forms handles external respondents.

Where Forms is most powerful is when paired with Power Automate. Form submission triggers a flow: send a confirmation email, create a record in Lists, post a Teams notification, start an approval. The form becomes the front door to a workflow rather than just a data collection tool. Suddenly your form-driven processes scale without manual work.

When you’ll use this

• When you need to collect the same information from multiple people.
• When you’re tired of parsing email replies into a spreadsheet manually.
• When you need surveys, registrations, or intake forms.
• When you want responses to trigger automation.

How to do it

1. Open Microsoft Forms via the App launcher.
2. Click + New Form.
3. Add a clear title and description.
4. Add questions one at a time, choosing the right type (text, choice, rating, date).
5. Use branching logic if some questions only apply in certain scenarios.
6. Preview and test the form yourself before sending.
7. Click Share to get a link or QR code.
8. Optionally connect to Power Automate for response-triggered automation.

Best practices

• Keep forms short. 5-10 questions max for most cases. Long forms = abandoned forms.
• Use the right question types. Choice for categories, not free text. Date for dates.
• Test before sending. 30 seconds testing prevents 100 confused respondents.
• Send a thank-you/confirmation message. Closes the loop with respondents.

Common mistakes

• 30-question forms. Most people don’t finish.
• Free-text fields where Choice would work. Inconsistent data; impossible to analyse.
• No testing before sending. Embarrassing typos and broken logic discovered by recipients.
• Asking ‘just email me’. Slower, lossier, and creates work for both sides.

↑ Back to top ↑ Back to list

Forms responses live in Microsoft Forms by default and can be exported or analysed. Knowing how to surface them — and what to do with them — turns data collection into action.

Once your form is live and responses are coming in, Microsoft Forms gives you a built-in Responses view: real-time count, per-question summaries with charts (where applicable), and a list of all individual responses. For most simple cases — a feedback form, a registration, a quick poll — this view is enough to see what’s happening.

For deeper analysis or reporting, export to Excel. The export gives you one row per response with all fields as columns — clean structured data you can pivot, chart, or share. This is the right path when responses need to feed into a larger dataset, when you want to filter by attributes, or when you need to share findings with people who don’t have access to Forms.

The most powerful pattern is connecting form responses to Power Automate. Each response can trigger a flow: confirmation emails, item creation in Lists, Teams notifications to specific people, approval workflows. Now the form isn’t just collecting data — it’s powering a process. The data flows where it needs to go automatically.

When you’ll use this

• When you’ve collected form responses and need to review them.
• When you want to share results with stakeholders.
• When you need to do analysis or reporting on the responses.
• When responses should feed into another system or workflow.

How to do it

1. Open the form in Microsoft Forms.
2. Click the Responses tab.
3. Review the summary view (counts, charts, individual responses).
4. Click Open in Excel to export structured data.
5. Use Excel for deeper analysis (pivots, charts).
6. If responses should drive a workflow, build a Power Automate flow.
7. Share findings appropriately (email, Teams, SharePoint page).

Best practices

• Review responses regularly. Daily for active surveys; weekly for slower ones.
• Export to Excel for serious analysis. Forms summary is good for overview; Excel for depth.
• Close the loop with respondents. Tell them what came of their input.
• Connect to Power Automate where appropriate. Manual processing of responses gets old fast.

Common mistakes

• Collecting responses and never analysing them. Wasted respondents’ time.
• Manual processing of responses you should automate. Forms + Power Automate = scalable.
• No follow-up with respondents. They’re left wondering if their input mattered.

↑ Back to top ↑ Back to list

Keyboard shortcuts compound. Five shortcuts saved 2 seconds each, used 50 times a day, is 8 minutes daily — 30 hours a year. Learn the few that matter most.

Most people use computers with mouse-first patterns — every action is a click. Keyboard shortcuts replace clicks with keystrokes, and across hundreds of actions per day, the time saving is real. The trap is trying to learn all the shortcuts, getting overwhelmed, and giving up. The fix is to learn 5-10 that matter most for your work, build them into muscle memory, and add more over time.

The universal shortcuts work across most apps: Ctrl+C copy, Ctrl+V paste, Ctrl+Z undo, Ctrl+Y redo, Ctrl+S save, Ctrl+F find, Ctrl+A select all. Microsoft 365 specific: Ctrl+Shift+T reopen closed tab, Ctrl+Tab cycle browser tabs, Alt+Tab switch apps, Win+L lock screen. Office apps: Ctrl+B bold, Ctrl+I italic, F12 Save As. Learn these and you’ve covered 80% of common actions.

Per-app shortcuts matter too. Outlook has Ctrl+R reply, Ctrl+Shift+R reply all, Ctrl+N new email, Ctrl+Enter send. Teams has Ctrl+E search, Ctrl+1-9 switch tabs. Excel and Word have dozens of useful ones. Pick a handful per app, learn them deliberately for a week, and they become automatic. The investment pays back forever.

When you’ll use this

• When you’re spending too much time clicking through menus for routine actions.
• When you want to work faster without buying new tools.
• When you’re new to Microsoft 365 and want to set up good habits.
• When you want to look like a power user (and actually be one).

How to do it

1. Identify 5-10 shortcuts most relevant to your daily work.
2. Print them or pin them visibly until they’re memorised.
3. Force yourself to use them — resist reaching for the mouse.
4. Add new ones gradually as the first set becomes automatic.
5. Use the in-app help (Alt key in Office, ? key in many web apps) to discover more.

Best practices

• Start with universal shortcuts. Ctrl+C/V/Z/S/F/A — they work everywhere.
• Learn per-app shortcuts for the apps you live in. Outlook, Teams, Excel.
• One new shortcut per week. Sustainable; compounds.
• Pin a cheat sheet until habits form. Then stop needing it.

Common mistakes

• Trying to learn 50 shortcuts at once. Overload; you abandon the project.
• Not committing to using them. Mouse is faster initially; resist.
• Forgetting that Office shortcuts often work in browser apps too. Same shortcuts; same payoff.

↑ Back to top ↑ Back to list

Quick Steps turn a sequence of email actions into a single click. The five minutes to set them up saves hours over the year.

Quick Steps are Outlook’s automation for email — sequences of actions you can trigger with a single click or keyboard shortcut. The classic example: ‘File and Mark Read’. Instead of clicking Mark Read, then dragging to a folder, then clicking back to inbox, you click one Quick Step button and all three happen at once. Multiplied across the dozens of emails you process daily, it’s significant time saved.

Built-in Quick Steps include common ones: file to a specific folder, reply and delete, forward to a manager, mark as task. Custom Quick Steps let you build your own — any combination of actions you do repeatedly. Five custom Quick Steps tuned to your inbox patterns can transform email processing from a slog to a series of single clicks.

The setup investment is small: Outlook → Home tab → Manage Quick Steps. Define the sequence, name it clearly, optionally assign a keyboard shortcut. Then use it. The first few times feel slow because you’re still thinking about which Quick Step to use; within a week, it’s automatic. Email becomes calmer because the routine processing is faster.

When you’ll use this

• When you do the same sequence of email actions repeatedly.
• When you’re processing a high volume of email and want to speed up.
• When you want to file emails to specific folders consistently.
• When you’re moving from folder-heavy to Quick Step-driven email management.

How to do it

1. In Outlook (desktop), go to Home tab → Quick Steps group.
2. Click Create New or Manage Quick Steps.
3. Add a name and choose actions (move to folder, mark read, forward, etc.).
4. Optionally assign a keyboard shortcut.
5. Save and use from the Home tab or via shortcut.

Best practices

• Build 3-5 Quick Steps for your most common patterns. File, follow-up, archive.
• Use clear names. ‘File to Customer X’ is clearer than ‘Quick Step 1’.
• Assign keyboard shortcuts to the most-used ones. Even faster.
• Review quarterly. Adjust as your inbox patterns change.

Common mistakes

• Not setting up Quick Steps because they ‘sound complicated’. 5 minutes of setup; hours saved.
• Generic Quick Step names. ‘Quick Step 1’, ‘Quick Step 2’ — useless.
• Building 20 Quick Steps you can’t remember. Stick to the few you’ll actually use.

↑ Back to top ↑ Back to list

Rules sort, file, flag, or auto-respond to emails based on conditions. Set them up once, and Outlook handles routine email processing without you.

Rules in Outlook are conditional automations: if email matches X, do Y. The conditions can be sender, subject keywords, recipient, attachments, date — any combination. The actions can be move to folder, flag, mark read, forward, delete, alert, or run a script. A few well-tuned rules can dramatically reduce inbox noise — newsletters auto-filed, notifications routed to a ‘noise’ folder, urgent emails auto-flagged.

The classic productive setup: rule that files all your CC’d emails into a ‘CC’ folder (you’ll review when you have time, but they don’t clutter the main inbox). Rule that flags emails from specific clients or your manager. Rule that moves automated notifications to a ‘System’ folder. Rule that auto-tags emails about specific projects. Combined, these rules cut your visible inbox to maybe 30% of what arrives — leaving you with the emails that actually need your attention.

Rules can be over-engineered. The trap is creating 30 rules with complex conditions and then forgetting what they do — eventually a rule misfires and an important email ends up filed somewhere you never look. Keep rules simple: 5-10 well-tested rules with clear purposes. Review them quarterly. Disable any that no longer match your workflow. Rules are useful when they’re maintained.

When you’ll use this

• When the same kinds of emails arrive repeatedly and need the same treatment.
• When your inbox is buried in newsletters and notifications you don’t need to see immediately.
• When you want emails from specific senders to stand out or be filed.
• When you’re moving toward a more structured email management system.

How to do it

1. In Outlook, go to File → Manage Rules & Alerts.
2. Click New Rule.
3. Choose a starting template or create from scratch.
4. Define conditions: from, subject contains, sent to, etc.
5. Choose actions: move to folder, flag, forward, etc.
6. Optionally add exceptions.
7. Name the rule clearly and save.
8. Test by sending or receiving a matching email.

Best practices

• Start with 3-5 rules. Add more only when proven useful.
• Use clear rule names. ‘CC me – file to CC folder’ is clearer than ‘Rule 1’.
• Review rules quarterly. Disable ones no longer needed.
• Test rules after creating. Don’t trust them blindly.
• Be careful with auto-delete. Test thoroughly before enabling.

Common mistakes

• 30 rules nobody can remember. Some misfire; trust evaporates.
• Auto-delete rules without thorough testing. Important emails disappear silently.
• Rules referencing email addresses that change. Rule stops working; you don’t notice.
• Over-complex conditions. Hard to maintain; harder to debug.

↑ Back to top ↑ Back to list

Out-of-Office is a small thing that signals professionalism and prevents anxiety. Set it up properly: clear message, alternate contact, sensible dates.

Out-of-Office (OOO) auto-replies tell senders you’re away, when you’ll return, and (ideally) who they should contact instead. Done well, they manage expectations smoothly — senders know not to expect a quick reply, urgent things get rerouted, you can switch off without inbox anxiety. Done badly (no OOO at all, or OOO that says nothing useful), they leave senders chasing you and your inbox piling up unhelpfully.

A good OOO has four elements: when you’re away, when you’ll return, who to contact for urgent matters, and (optionally) what kind of urgency warrants the alternate contact. Skip the personal details — ‘I’m at my parents’ wedding in Italy’ isn’t necessary. Senders need to know you’re unavailable and what to do, not your life story.

Outlook supports separate messages for internal and external senders — useful when you want to give colleagues more detail than external contacts. Set both. Schedule them with start and end dates so they activate automatically and turn off when you return — no need to remember. And remember: an OOO that’s still active a week after you’ve returned is awkward for everyone.

When you’ll use this

• When you’re going on leave (annual leave, parental leave, conference, sick leave).
• When you’re away from email for a meaningful period (a day or more).
• When you want to set expectations with senders during reduced availability.
• When you’re handing off responsibilities and want others to know who to contact.

How to do it

1. In Outlook, click File → Automatic Replies.
2. Turn on Send automatic replies.
3. Set start and end dates.
4. Write the internal reply (concise, with alternate contact).
5. Optionally write a separate external reply (briefer, less detail).
6. Save and confirm it’s active.
7. Check it turns off automatically when you return.

Best practices

• Keep messages brief. When you’re away, when you return, who to contact.
• Schedule with end dates. Don’t rely on remembering to turn it off.
• Test by sending yourself an email. Confirms the OOO is working.
• Brief the alternate contact. Don’t surprise them with redirected requests.

Common mistakes

• No OOO at all when away. Senders chase, inbox piles, you return to chaos.
• OOO with too much personal detail. Unprofessional; not what’s needed.
• Forgetting to turn it off. ‘You’re back?’ from people getting your OOO three days later.
• Naming an alternate contact who doesn’t know. Awkward for them, embarrassing for you.

↑ Back to top ↑ Back to list

Focused Inbox separates important emails from clutter automatically. Trained well, it cuts your visible inbox by half — letting you focus on what matters.

Focused Inbox is Outlook’s machine-learning sorter. It analyses your email behaviour — who you reply to, what you read, what you ignore — and divides incoming email into two tabs: Focused (likely to matter) and Other (likely not). Important emails come to Focused; newsletters, notifications, and bulk emails go to Other. You can move emails between tabs to train the system.

When it works well, Focused Inbox transforms email. Instead of seeing 200 emails a day, you see 60 in Focused — the ones that actually need your attention. Other still receives everything; nothing is lost; you just don’t see the noise unless you choose to. For people drowning in inbox volume, this single feature is genuinely transformative.

Training matters. The first few weeks, move misclassified emails between tabs (Move to Focused, or Move to Other). The system learns. By week three, it’s usually well-calibrated. If it’s still misclassifying, the misclassification is probably about emails you’ve been treating inconsistently — read carefully sometimes, ignored other times. Decide how you actually want to handle that sender, then train the system accordingly.

When you’ll use this

• When your inbox volume is high and you’re missing important emails in the noise.
• When you want to see less without unsubscribing from everything.
• When you’re moving toward a more disciplined email approach.
• When you want to spend less time scanning your inbox.

How to do it

1. In Outlook, go to View → enable Show Focused Inbox.
2. Two tabs appear: Focused and Other.
3. Initially, the system uses defaults; over time it learns your patterns.
4. When emails are misclassified, right-click → Move to Focused or Move to Other.
5. Spend a few weeks training; the accuracy improves significantly.
6. Check Other periodically (daily or end-of-week).

Best practices

• Train it actively for the first 2-3 weeks. The investment pays back forever.
• Check Other at least daily. Things still arrive there.
• Combine with rules for auto-filing. Belt and braces.
• Trust the system once it’s trained. Stop second-guessing every classification.

Common mistakes

• Not training the system. Accuracy stays low; you stop trusting it.
• Never checking Other. Important emails buried; you miss them.
• Turning it off because ‘it’s not perfect’. Imperfect is dramatically better than no filter.

↑ Back to top ↑ Back to list

Flagging an email turns it into a task with a follow-up date. Better than leaving it in the inbox ‘to remember’ — flags surface in To Do and on the calendar.

Most people have a habit of leaving important emails unread or starred in their inbox ‘to come back to later’. The problem is, the inbox is also where new mail arrives — so ‘come back to later’ becomes ‘lose track of among the new arrivals’. Flags solve this. A flagged email becomes a task with a due date, surfaced separately from the inbox itself, integrated with To Do and the Outlook calendar.

The flag adds the email to your To Do list automatically. You can set a flag for today, tomorrow, this week, next week, or a custom date. The email stays in the inbox (so you can find it via search or browse), but the task is now tracked separately in To Do. You can add notes, link related emails, and check it off when complete.

What this prevents is the ‘inbox-as-task-list’ antipattern. Email is for messages; tasks are for things you need to do. Flagging takes the right emails out of the messaging space and puts them in the task space, where they belong. Combined with rules for auto-filing and Focused Inbox for filtering, flags complete the system: incoming email gets sorted, important things get flagged as tasks, the inbox stays clean.

When you’ll use this

• When an email contains an action you need to take but not right now.
• When you want to remember to follow up on something at a specific time.
• When you’re trying to break the ‘inbox as task list’ habit.
• When you want emails to surface alongside your other tasks in To Do.

How to do it

1. In Outlook, right-click an email → Follow Up.
2. Choose a flag (today, tomorrow, this week, custom date).
3. The email gets a flag icon and appears in your To Do list.
4. Open Microsoft To Do to see flagged emails alongside your tasks.
5. Mark the flag as complete when you’ve actioned it.
6. Use search if you need to find specific flagged items later.

Best practices

• Flag with realistic due dates. ‘Today’ for things due today; ‘Next week’ for things that aren’t urgent.
• Action flagged emails in To Do, not the inbox. Work the task, not the inbox.
• Mark complete promptly. Otherwise flag list grows useless.
• Combine with Focused Inbox. Filter first, flag the important.

Common mistakes

• Flagging everything. Flag list becomes as overwhelming as the inbox.
• Never reviewing the flag list. Flags pile up; system becomes useless.
• Flagging instead of actioning. Flags are ‘do later’, not ‘never do’.

↑ Back to top ↑ Back to list

Inbox cleanup is a periodic ritual, not a one-off project. A 30-minute cleanup once a quarter prevents the ‘inbox bankruptcy’ moment.

Most people’s inboxes accumulate. Newsletters that no longer get read. Notifications from systems that no longer matter. Old conversations that ended months ago. Files attached to emails when the file should have been a SharePoint link. Over time, the inbox becomes a graveyard of half-relevant content. Cleanup is the discipline of clearing this out periodically — not all at once, but in 30-minute sessions every few weeks.

Outlook has tools to help. Conversation Cleanup removes redundant messages from email threads — when a long thread has 20 replies, often the latest message contains all the previous ones, so the earlier 19 are redundant. Cleanup deletes them, leaving only the most current. Sweep handles bulk deletion or filing of messages from specific senders. Search and select lets you find old emails by date or sender and delete in batches.

The deeper move is unsubscribing. Most inboxes are clogged with newsletters, notifications, and promotional emails the user is no longer interested in. Outlook’s Unsubscribe feature (visible at the top of subscription emails) makes it one click. Spend 10 minutes in a cleanup session unsubscribing from things you don’t read; volume drops significantly going forward. Cleanup isn’t just deleting old emails — it’s stopping new noise.

When you’ll use this

• Quarterly, as a regular ritual.
• When inbox volume is becoming overwhelming.
• When you’ve been heads-down on a project and the inbox accumulated.
• When you’re starting fresh in a new role and want a clean baseline.

How to do it

1. Block 30 minutes for cleanup.
2. Use Sweep for bulk actions on specific senders.
3. Use Conversation Cleanup to remove redundant thread messages.
4. Sort by sender and delete entire categories of newsletters.
5. Unsubscribe from anything you no longer read.
6. Archive old projects; delete irrelevant content.
7. Empty the deleted items folder when finished.
8. Schedule the next cleanup in your calendar.

Best practices

• 30-minute sessions, not 4-hour marathons. Sustainable cadence.
• Unsubscribe aggressively. Reduces future volume.
• Use Sweep and Conversation Cleanup. Faster than manual deletion.
• Schedule the next session. Otherwise you forget until the next crisis.

Common mistakes

• ‘Inbox bankruptcy’ — declaring all emails irrelevant and deleting everything. Loses real content.
• Cleaning once a year for 8 hours. Bad cadence; unsustainable.
• Not unsubscribing. Volume returns immediately.

↑ Back to top ↑ Back to list

Microsoft To Do is your personal task system — flagged emails, manually-added tasks, assigned Planner items, all in one place. Used well, it’s the closest thing to a unified inbox.

Microsoft To Do is the personal layer of Microsoft 365’s task ecosystem. It’s not a project management tool — it’s a daily task list. What goes in: emails you’ve flagged for follow-up, tasks you’ve added manually, tasks assigned to you in Planner. What comes out: a clear daily view of what you need to do today, this week, and beyond. For people drowning in commitments, To Do is genuinely calming.

The killer feature is My Day — a fresh, daily-curated list you build at the start of each day. You’re not looking at your full backlog (which is overwhelming); you’re choosing the 5-10 things you’ll do today. The rest stays in your task pool but isn’t in your face. At end of day, anything not done either rolls to tomorrow’s My Day or stays in the backlog. The discipline of a daily list — separate from the backlog — changes how productive a day feels.

To Do also integrates across the suite. Flagged emails appear automatically (see W-13). Planner tasks assigned to you appear automatically. You can add tasks manually for things outside Microsoft 365. The result is one place to see your tasks regardless of where they originated. Combined with a daily My Day routine, it’s how busy people stay on top of work without losing track of what matters.

When you’ll use this

• When you have tasks scattered across email flags, Planner, and your head.
• When you want a single place to see everything you need to do.
• When you want a daily-focused list separate from your full backlog.
• When you’re building a personal productivity system that scales.

How to do it

1. Install Microsoft To Do (web at to-do.office.com, desktop apps, mobile apps).
2. Sign in with your work account.
3. Tasks from Planner and flagged emails appear automatically.
4. Add manual tasks via the + button.
5. Each morning, review tasks and add the day’s priorities to My Day.
6. Work through My Day during the day.
7. End of day: clear completed; roll over what’s left if needed.

Best practices

• Use My Day daily. Choose 5-10 things; not the whole list.
• Trust the integrations. Flagged emails and Planner tasks come in automatically.
• Don’t over-engineer with categories and lists. Default Tasks list works for most.
• Mark tasks done promptly. Visible progress fuels momentum.

Common mistakes

• Not using My Day. Daily focus disappears; overwhelmed by full list.
• Building 15 different lists for different categories. Over-engineering; system collapses.
• Adding tasks to To Do but not actioning them. List grows; stops being trusted.

↑ Back to top ↑ Back to list