Need Map
Shift from MS teams tech perspective to team/organization design
perspective
Are you using all features of 365
for best possible collaboration
An insight on how to collaborate better
MS teams
Jobs to be done
Quality of work
• Required
Knowledge base
Connection to expert
Flexibility
Feel good
• Help others
• Resolve conflict
• Avoid conflict
• Get kudos
Processes
• Which process need to aligned and optimized for success
Develop a sense of control in context-
recommendations
Control over work environment
 —depends on type of work. Control may not be high for management team, but
may be high for coding/analytics team.
Giving presentation
 Structure
 Feedback
oLearning
oExcellence in performance
Metrics for measuring the performance
Getting feedback
 Ideating
 Review
 Critique
System Support required
Expert connect
Connecting to experts
for resolving issues
•Learning paths
•critique
Information search over load
Ability of find information
Awareness of which information is where
Purge un-ncecessary information
Duplication of systems
•There should be one system for communication-MS teams or email
Sharing of files
SharePoint vs OneDrive
Search and statistics
Search and statistics related to systems should be available at one place
Recommendations for files
Merge files
Knowledge management insights analytics
Wellbeing support
Socialization channels
• Ideation
• Team building
• Chaupal/Adda Channel
• Celebration
• Team bravo
Support of leadership
• One on one with CXO
Integrate systems
Our observations also point to a larger problem: when many collaboration tools
are available, groups have a hard time determining which tool will best support
their needs. As a result, they sometimes make unexpected or sub-optimal decisions,
choosing a tool that does not fit well with the collaborative characteristics of their
team.1
Need-Product
Tech focused
• Reporting-adoption and
Usage
• Governance and
compliance
• Performance and reliability
Org design focused
• Change management
• Quality of work and
productivity
• Wellbeing
•Descriptive bar charts
•Line charts
•Location charts
•Network graphs
•Heatmaps
•Lists
•Insights
• Comparisons
• Outliers
• Habits
• Persistent trend
• Positive
• negative
Type of charts
https://www.modalitysystems.co
m/software/teamwork-analytics
https://martellotech.com/solutions/microsoft-365-monitoring/
https://martellotech.com/solutions/mitel-performance-analytics/
List of “must Use” apps
Power automate
•Integrate greythrlogin to teams
•Get emailnotifications in teams
•Get jira notifications in teams
•Other notifications and link to it
Planner
•Integrate email and team messages to planner
•Integrate jira to planner
•Shared todo lists
•Complete visibility on who is doing what
•Who has spend how much time on which task
Quality of review app-TO be developed
•What was the quality of review?
•–time spent on review by manager
•Asynchronous deliverables shared .
•Comments on asynchronous deliverable by Manager/reviewer
Routine analytics
Burnout metrics Dashboard
•To be develoed
•Network analytic
•Planner
•Quality of review

Colloboration analytics- Need map from tech design to org design

  • 1.
    Need Map Shift fromMS teams tech perspective to team/organization design perspective
  • 2.
    Are you usingall features of 365 for best possible collaboration An insight on how to collaborate better
  • 3.
  • 4.
    Jobs to bedone Quality of work • Required Knowledge base Connection to expert Flexibility Feel good • Help others • Resolve conflict • Avoid conflict • Get kudos Processes • Which process need to aligned and optimized for success
  • 5.
    Develop a senseof control in context- recommendations Control over work environment  —depends on type of work. Control may not be high for management team, but may be high for coding/analytics team. Giving presentation  Structure  Feedback oLearning oExcellence in performance Metrics for measuring the performance Getting feedback  Ideating  Review  Critique
  • 6.
    System Support required Expertconnect Connecting to experts for resolving issues •Learning paths •critique Information search over load Ability of find information Awareness of which information is where Purge un-ncecessary information Duplication of systems •There should be one system for communication-MS teams or email Sharing of files SharePoint vs OneDrive Search and statistics Search and statistics related to systems should be available at one place Recommendations for files Merge files Knowledge management insights analytics
  • 7.
    Wellbeing support Socialization channels •Ideation • Team building • Chaupal/Adda Channel • Celebration • Team bravo Support of leadership • One on one with CXO
  • 8.
    Integrate systems Our observationsalso point to a larger problem: when many collaboration tools are available, groups have a hard time determining which tool will best support their needs. As a result, they sometimes make unexpected or sub-optimal decisions, choosing a tool that does not fit well with the collaborative characteristics of their team.1
  • 9.
    Need-Product Tech focused • Reporting-adoptionand Usage • Governance and compliance • Performance and reliability Org design focused • Change management • Quality of work and productivity • Wellbeing
  • 11.
    •Descriptive bar charts •Linecharts •Location charts •Network graphs •Heatmaps •Lists •Insights • Comparisons • Outliers • Habits • Persistent trend • Positive • negative Type of charts
  • 12.
  • 13.
    List of “mustUse” apps Power automate •Integrate greythrlogin to teams •Get emailnotifications in teams •Get jira notifications in teams •Other notifications and link to it Planner •Integrate email and team messages to planner •Integrate jira to planner •Shared todo lists •Complete visibility on who is doing what •Who has spend how much time on which task Quality of review app-TO be developed •What was the quality of review? •–time spent on review by manager •Asynchronous deliverables shared . •Comments on asynchronous deliverable by Manager/reviewer Routine analytics Burnout metrics Dashboard •To be develoed •Network analytic •Planner •Quality of review

Editor's Notes

  • #5 Challenges Emotional Security and privacy Trust for organization Trust in team Joy of working from home Social   Not building rapport with the virtual team. ... Difficulties in aligning the remote team. ... Bad communication. ... Not creating a culture of trust. ... Unconstructive or inconsistent feedback. ... Trying to replicate in-office work process. ... Micromanaging the team. Too many tools Wrong person Issue with timezones Overlooking Team Interactions. ... Failure to Communicate Expectations. ... Poor Communication. ... Micromanaging Your Team. ... Failing to Focus on Diligence. ... Rushing Through Virtual Meetings. ... Over-Reliance on Emails. ... Improper Management of Remote Team's Performance.