Why Do Team Members Stay?
This relationship might be the biggest indicator of whether your best people stay, and you give the person in charge of this relationship almost no training on how to manage it effectively.
Please, make it make sense.
-
-
Worth Reading – The trap of being promoted from within
When you get the title, people will bring you things and hand off responsibility to things that you didn’t know existed. Even though you were sitting right there, in the team that you now lead, you don’t know how many things the previous person in that chair never bothered to tell you about, or the relationships across other teams that made their life easier that you need to build. Many of those things didn’t just happen; effort went into knowing what to do and who to talk to.
-
Worth Reading – Good Leaders Presume Team Members Feel Undervalued and Underappreciated
It’s a difficult thing, in the busy work world we all live in, to make sure your people are looked after and appreciated. It’s very easy to take them for granted because you trust them to do their work. I’m not saying you should micromanage them, but showing an interest in them and their work would help them feel like part of the team. Letting other things get in the way creates an issue. One that may lead your best performers to leave for a place where they feel more appreciated.
-
-
Create Certainty Where You Can
Like it or not, your team is dealing with a ridiculous amount of uncertainty in and out of the office. Most of it is beyond our control. When we have the opportunity to create less of it, we should do so. We have the opportunity to make a difference for our team, as human beings, just by communicating and setting clear expectations. Why wouldn’t we?
-
Worth Reading – RIM Is Moving Upstream
Instead of starting your work in a blank Word document or spreadsheet, start in Copilot chat, then move it to a Copilot page, which is a Loop file. From there, you drop part of the page, a component, into chat for live collaboration with your team, or you work together in the Loop app, with Copilot assisting again and drop the new draft into an email, linked to the web version for easier editing by the entire team, until finally, at the very end of this process, you create a PDF of the final product, and add it to your “records” location.
Thus, only the final version ever gets stored as a record. All the prior versions are gone. Work that is still in progress is not a record, but accessible to AI tools. This is the conundrum for RIM.
