Teams Framework
Our iWorkplace framework gives you thinking, tools, training and a plan to take back control and get more value from this amazing interface.
Like many organisations, we plunged head first into ad-hoc Teams use. The outcome was not good and most of us reverted to email...
Fast forward to now, and we couldn't imagine not using Teams as our primary way of working together and with customers.
It's also central to how we curate and build know-how and run our core business processes. We have seen this repeated in the implementations we have done for customers.
... to do a great job. We used to have overflowing email in-boxes, and frustration searching to get together all comms on a topic.
Now its all in a channel .. as all the information I need on a topic is together and tabs give access to relevant resources.
All business activities and knowledge centres are covered. When using Teams, correct channel design was vital. We almost never have just the General channel. Channels are created per customer, knowledge topic, report, job or assignment etc. In some cases standard Teams and workspace templates are activated via a self-service wizard.
Metadata. The designs include inherited as well as auto classified metadata to drive search, navigation, browse and R&D.
"Just right". If the breadth of a channel was too narrow, we end up with too many places to go to collaborate. If it's too wide, then conversations overlap, and threads get lost. This is what we refer to as the ‘Goldilocks’ effect where the trick is to design channels to be “just right”.
If a channel is too tightly defined, then you have the same people operating in multiple channels, if it is too wide, you will have trouble finding what you are looking for.
Death comes quickly to Teams, if it's not obvious where to collaborate or find what you need.
For instance, for conferences do we have a team per conference or a team for all conferences and a channel for each?
So this needs consultation then a binding decision - one way or the other.
Ad-hoc Teams? It also means we lock down or limit self created ad-hoc teams that will just sow confusion. If someone wants a Team they can easily check what Teams are in use already and then request one if needed.
Members only. When an out of the box Team is created, members have administrative rights and no one else even knows the Team and its library exist. This is a recipe for information accidents and duplication.
vs Organisational asset. So Teams Framework allows administrator rights to be limited, and for most Teams adding permissions for all staff to see and search for the library content. Search results can be refined by Team and channel.
External guests? This used to be painful to setup and manage. Now customers can collaborate and share files securely through our Smart Guest Mgmt App
We have many case files - proposals, reports, projects, campaigns, knowledge showcases etc
Lifecycle managed. We have a channel for each of these cases and through our Apps the ability to close these when the work is done. This removes clutter in Teams but allows the files to be secured in SharePoint, and disposed of by R&D schedule
Teams Framework powers collaboration and getting work done in 50+ New Zealand organisations. Its been a game changer for many through lockdowns and WFH. Contact us for more information.
Our iWorkplace framework gives you thinking, tools, training and a plan to take back control and get more value from this amazing interface.
Whether you're already facing these challenges or are worried you might;
we can help.
By default anyone can create a team (and its associated SharePoint site). This leads to multiple Teams and confusion about where to work
“Where did we work on that report?"
As use grows over time info gets compartmentalised & mistakes happen
By default Team owners & members can change key settings on the SharePoint sites - this can make it harder for users to use and even access this info
Personal or sensitive information held in Teams can become a ticking time bomb. Is content being held in Teams that should have been disposed of or secured?
All of the above raises risk and potential liability for indefensible disposal, not to mention making it even harder to gather the info needed for OIA, LGOIMA or Ministerial requests
You and others getting disillusioned and returning to email, meetings, and file share use
In 2020, Information Leadership was one of only 41 partners worldwide with this ranking and the only Kiwi company. This is for our proven expertise in Compliance/Records Management and Implementation.
We are an authorised supplier of Cloud Transition Services on the NZ Government ‘Marketplace’ - it is now simpler, quicker and more cost-effective for public sector agencies to access our services
Leaders in setting up Microsoft 365 digital workplaces so they are easy and flexible to use, while giving you the confidence and control to manage business-critical information and risks
For the second year in a row, Information Leadership has won 'Empowering Employees' at the Microsoft New Zealand Partner of the Year Awards. As well as Highly Commended for the 'Modern Workplace' Award in 2019.
Are you ready to take the next step in your M365 journey or would like to talk to our team about how we can bring your Teams under control?
As an organisation of information management experts who live and breathe Microsoft products, we saw the appeal and potential of Teams. But soon after adopting Teams, we broke it.
Thought Leadership coming soon.
By default anyone can create a team (and its associated SharePoint site). This leads to multiple teams and confusion about where to work
Why can't I access all the information I need? Teams lock down access and search to members of the team and information becomes dangerously compartmentalised
By default Team owners and members can change key settings on the SharePoint sites - this can make it hard for users to use and even access this info
Personal or sensitive information held in Teams can become a ticking time bomb. Is content being held in Teams that should have been disposed of or secured?
All of the above raises risk and potential liability for indefensible disposal, not to mention making it even harder to gather the info needed for OIA, LGOIMA or Ministerial requests
You and others getting disillusioned and returning to email, meetings, and fileshare use
Avoid ad-hoc messes that need to be sorted out later
Users request Teams via a simple form, ensuring they are reviewed, meet needs, and you avoid duplication
Achievable on a minimal budget with only a 2-3 week set up time
Standardised document libraries and permissions, giving you great search, retention & disposal, and meeting your government mandated requirements
We have methods you can use to quickly review and cleanup and/or consolidate Teams - so you go from thousands to tens
Russell Craig
Microsoft New Zealand
National Technology Officer
Take a deep dive into Teams and all its distractions in our webinar.
Let's talk Teams.