| Table of Contents | ||
|---|---|---|
|
What is Team Directory?
Refer to this document to understand what Team Directory is and what challenges it is designed to help solve for: at the heart of creating a single source of truth for teams and team members, is it the foundation to build upon for people, teams, strategy, outcomes, work and much more! More info on the parent page Team Directory
Team Directory roll out approach
...
Customised tenant established with SSO sign in
People and demand teams exist in TeamForm
TeamForm is the source of truth for delivery structures
Gain insights on team composition and capacity availability
Data enrichment for more up to date team composition, capacity availability insights and employee engagement surveys
Area | Activity |
SSO configured as per (Single Sign On) configured to your organisation’s preference solution Standard SSO role based assess access defined and implemented | |
People Import | Manual CSV import of people (HRIS) data brought into TeamForm
|
First iteration of delivery team structures represented in TeamForm(often making something visible, prompts clarifications and changes). | |
People assignment to delivery teams | People are in delivery team structures People memberships have been validated by key stakeholders Process to membership updates have been designed, signed off and embedded with the objective that TeamForm is the source of truth for delivery structures. |
Data Availability | Real-time team & people data CSV extract |
...
Area | Activity |
|---|---|
Delivery Team Structures | All delivery team structures and types are validated, improved where necessary and are continuously maintained in TeamForm Optional: Delivery teams have team description and linkages to their Jira work tracking board (where possible) such as Jira boards and company strategy/objectives |
People Import (i.e supply structure) | Automated file transfer of people (HRIS) data brought into TeamForm, with additional data fields includingsuch as:
|
Other data integration | Additional data sets brought into TeamForm from external systems via data integrations:
|
Additional data source of truth in TeamFormVisualisation and linkage of other data set | Where available if there are job titles that are not equivalent to someone’s role titles, the roles are reflected using tags Another typical example is funding source from your finance system. |
Additional data source of truth in TeamForm | All additional data sources where TeamForm is the source of truth for have been brought into the platform. Examples include platform ownership, assets, funding sources, etc |
Reporting | TeamForm data is connected into the organisation’s data lake or reporting BI tool via API |
Secondary supply structure (by exception when needed) | Secondary supply structures brought into TeamForm |
...
Use the table below to help you understand what other features can be done with your Team Directory! Remember they are optional and should only be brought into the platform when your organisation is ready for it and sees value in it.
Advance TeamForm Use Cases
Workforce Planning
Short & long term workforce forecast
Org Design
Assess team structures against principles
Manage & cost OKRs
Financials
Blended rate cards based on your supply hierarchy so that as you are planning or designing a team, users can get a high level estimation of what the team will cost
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
Benefit(s) of bringing the data into TeamForm | ||
People Import | HRIS reporting line - scheduled automated data transfer - safer, quicker and close to real time update of organisation movements i.e. number of people leaving and joining the org | |
Associations | Ease for users to find dependent teams and/or teams that Associations | Users can see the interdependencies between teams, codify interaction patterns such as Team Topologies, and show where teams share the same leader |
Employee images | Enhanced user experience especially if your organisation has a virtual working environment as it allows users to know who they are speaking with |
Optional: Additional foundational set up for further TeamForm use cases
We understand that every organisation is at a different maturity level and has different priorities therefore not all users will see the need to use all or any of TeamForm’s additional functionalities. However in the event that you do wish to explore the use of other additional TeamForm features, please use the table below to help you understand what extra data is required to be brought into the platform in order to unlock the full potentials in each of the TeamForm functionality use cases.
Ways of working principles | Giving TeamForm all your team archetypes from the start will allow you to:
|
| Status | ||||
|---|---|---|---|---|
|
People Data
HRIS reporting line - scheduled automated data transfer
Secondary supply structure (only consider if it’s a must required)
This information is critical to setting up the right process flow to how work demands can be triaged and approved from demand through to supply leads.
Tracking of data accuracy
Data accuracy is key for a successful roll out and adoption of TeamForm as users can focus on what the data is telling them knowing they can trust what they see rather than fixing the data so that it resonates with them. We can provide you a dashboard to help you monitor the data accuracy, making it easy for leaders to know what specifics they need to fix in TeamForm.
Employees' leave/holiday info
If not brought into TeamForm, it will impact:
The supply leaders' decision making during workforce planning to know who they can allocate against demand requests
Difficult for people in the organisation to know who is or isn’t around the team
Vacancies
If not brought into TeamForm, it will hinder the supply leaders' accurate view of how many roles they have available to meet demand requests.
However, when vacancies are brought into TeamForm, you need to consider how the vacancy management process is going to be for users as TeamForm do not support the traditional HR functionalities in managing the lifecycle of vacant roles.
| Status | ||||
|---|---|---|---|---|
|
Secondments
If not brought into TeamForm, it will impact:
The supply leaders' decision making during workforce planning to know who they can allocate against demand requests
Difficult for users to trace back to why there were certain people movements within the team for a specific period of team
| Status | ||||
|---|---|---|---|---|
|
...
Optional additional foundational set up for further TeamForm use case
There are additional data elements that need to be set up in Directory if you would like to use TeamForm’s advance use cases.
See Also:
| Child pages (Children Display) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|