2.0 invitation triggered when a team member is added to a team
It should be possible to add a team member to a team without notifying them and inviting them to access the team in 2.0. Managers may need to review a team confidentially and it is unhelpful for the team member to be made aware that they have been added to a team and have the ability to view the team. Could this be optional rather than automatic?
Comments: 19
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
21 Aug, '24
Bobbi KellyHighlighted comment
I have a lot of clients that use this tool to investigate who may make a good team going forward or swap profiles in and out to see where gaps could most effectively be closed. Being notified when this happens would cause many of my clients to drop Design. -
30 Apr, '24
Brian Gelt MergedTeam leaders may want to see how different people fit. They will likely not want those people to be notified.
-
30 Apr, '24
Bruce Hawkins MergedNeed the flexibility to add a potential member to a team without notification. This can allow a team to problem solve how to close a teams gaps to strategy. Especially a cross functional team where the existing team may have a list of candidates but want to understand how those drives would change the team before making a firm decision. That has been the power of Design Teams in Legacy. I've tactically used it that way and it's powerful. Also drives ownership of the team around the science and value of PI and also adoption as individual Talent Optimization leaders.
-
30 Apr, '24
Caroline Porter Admin Merged"Turn off notifications in Design 2" (suggested by <Hidden> on 2024-04-30), including upvotes (1) and comments (0), was merged into this suggestion.
-
01 May, '24
Melanie WoodSending an email to team members when they are added to a team could "trigger" people! People could unnecessarily question, "why is ___ adding me to a team?" I think this could separate people versus hoping to unite them.
-
01 May, '24
Rachael ReeceI also work with leadership in a planning/strategy stage to build task force teams, reorganizations or other special project teams and it would be premature for potential team members to see that they are being added without context. I would be concerned about this feature.
-
01 May, '24
Chris PalmerParticularly with moving to an unlimited number of teams, a lot of the value of the module is scenario planning. Aside from the confidentiality issues, the number of emails will be annoying if a person is added to multiple teams. Suggest finding another avenue to get people to sign in to the software.
-
01 May, '24
Julie HagovskyAgreed, especially if you are using this for assessing the shift of team dynamics by adding a new person to the team (not announced yet to the team) and looking to move someone within the organization to another team but, you don't want to tell them because it is part of succession planning/career planning. We should have a button to say "don't notify team members", etc.
-
08 Jul, '24
Bruce HawkinsScenario planning a huge plus of Legacy in Design...especially with the headcount option. Also...I would be sending out assessment invites long before this point in the process i'm thinking. IE would want to understand their Profile before vs inviting them to take the assessment and be added to the team at the same time. Who is going to be giving them a readback? What awareness do they have of the PI BA before an assessment shows up just because they were added to a team Seems like it would open up a lot of confusion.
-
08 Jul, '24
Robyn KnoxWe need the flexibility to keep the teams incognito, particularly for workforce planning and succession planning purposes. Also, this creates an issue if we will be facilitating the HPSW. We will need time to prepare for the workshop by reviewing the team type and strategy type, and we do not want to share the team with individual team members until the big "reveal."
-
10 Jul, '24
Chantal van der WaltPeople who have not been trained in PI should not be able to access the software and see team information and stuff like that. This is a tool for trained PI analysts in my opinion and allowing people to see the team information before a proper session gives them the opportunity to make some uninformed, preconceived opinions without understanding the tool and material.
-
30 Jul, '24
Diana RivenburghI concur with all prior comments about confidentiality for multiple reasons. One of the options in Legacy that has been very impactful is to go through a 1:1 Talent Strategy session with the senior leader and build context and preparation for the High Performance Team sessions. I sincerely hope that this will quickly move from "under consideration" to fixed.
-
01 Aug, '24
Jessica IvinsWe have seen this issue create friction in multiple UX research sessions. Some clients even stop using Design altogether because they're too nervous about inviting clients into the software to move forward.
-
01 Aug, '24
Becca VanDerveerBased on client feedback who just invested $20K in their ALF -- they do not feel comfortable using Design unless the automatic notifications are resolved. Unlikely clients would be willing to renew this product if they are afraid to use it. This should be resolved ASAP.
-
01 Aug, '24
Marla Jo NoelMany of my clients use Design when hiring. If the new hires can see the other team members' information, which should be private, you have taken away much of the advantage of Design. UGG!!!
-
13 Sep, '24
Beth FrielI am trying to set up a demo in my business account and if I add the prospect to a Design team, it will invite them to become a user. This is crazy. I can't imagine converting any of my current clients with Design if this is still in effect. Please change this asap.
-
11 Oct, '24
Lexie JonesI will lose my main client if this is not fixed. Their org needs to keep this info close hold as it has far reaching implications if team members find out ahead of time.
-
11 Oct, '24
Joe Kirschbaum AdminThank you for the feedback regarding the need for private teams in Design within PI2. We are in the process of decoupling team membership and software access, meaning when a team is created the creator has the ability to determine if this team is restricted or open. If restricted, no one who is added to the team is sent a software invitation. If open, everyone added to the team is sent an invite to become a software user of Design and has access only to that specific team. A screenshot of the design is included in this post for visibility into how this will look when creating a team. This work is actively being developed and will be available in production in November 2024.
-
11 Oct, '24
Joe Kirschbaum Admin"2.0 Design and Team Member Notification Option vs mandentory." (suggested by <Hidden> on 2024-04-30), including upvotes (4) and comments (2), was merged into this suggestion.
