Outlook, Teams and Portal Experience Quick Check
Three minutes. Ten questions. No personal details collected.
This self assessment highlights whether your service experience across Outlook, Teams, and the portal feels clear and connected, or quietly scattered.
Answer each question with Yes, Sometimes, or No. Click Show my result to see your score and the next step.
How it works
Scoring
Yes equals 2
Sometimes equals 1
No equals 0
Sometimes equals 1
No equals 0
Sections
Questions 1 to 5 look at channel clarity and flow
Questions 6 to 10 look at friction, coordination, and overall service pattern
Questions 6 to 10 look at friction, coordination, and overall service pattern
Channel clarity and flow
1
For common IT needs, do employees usually know whether to use the portal, email, or Teams?
Why this matters
If people are unsure where to start, they choose the safest or most familiar channel, which creates duplication and undermines the service pattern.
2
Do common service interactions usually happen in the channel that makes the most sense for the user?
Why this matters
When the interaction happens in the wrong place, people switch channels or create side conversations just to move one piece of work forward.
3
Can employees get help and track progress without needing to jump between multiple places?
Why this matters
If users need to move between Outlook, Teams, and the portal to stay informed, the experience feels heavier than it should and workarounds become normal.
4
Do important updates and approvals usually appear where people will actually notice and act on them?
Why this matters
It is not enough to send a notification. It has to land in the place where someone will see it quickly and know what to do next.
5
Do employees and approvers rarely miss or delay actions because notifications are easy to overlook?
Why this matters
Missed updates and delayed approvals are often a signal that the message is landing in the wrong place, with the wrong level of context, or with too much surrounding noise.
Friction and coordination
6
Are people rarely frustrated by duplicate, noisy, or low value notifications?
Why this matters
When too many updates feel generic or repetitive, people stop paying attention and the important messages lose their impact.
7
Can service desk and resolver teams progress work without constantly jumping between ServiceNow, Outlook, Teams, and side conversations?
Why this matters
If support teams rely on channel switching to keep work moving, the experience may look fine on the surface while hidden effort keeps building behind it.
8
Can urgent issues usually be coordinated without too much manual follow up, scattered threads, or side chats?
Why this matters
Urgent work exposes weak patterns quickly. If coordination depends on manual chasing or fragmented conversations, delays and confusion are almost inevitable.
9
Do common requests and approvals usually move forward without unnecessary manual chasing or fragmented handoffs?
Why this matters
Too much manual chasing usually means the service pattern is unclear, the notification design is weak, or the handoff between channels is not working cleanly.
10
Is there a clear shared understanding of what should stay in email, what belongs in Teams, and what should happen in the portal?
Why this matters
Without a shared pattern, each group creates its own habits. That makes the experience inconsistent and makes future improvement harder than it needs to be.
Your result
0
0 to 8
Work is scattered
9 to 15
Friction is building
16 to 20
Clear foundations