Відео

I think you mentioned that you would put a link to the webinar that you were talking about at the beginning of the episode and I do not see that link. Any chance you could go ahead and add it?

Thank you for this. This is EXACTLY what my organization needs.

This was very valuable content, specially for people new in Microsoft's Ecosystem. I would just like to add the Microsoft is a huge company, catering to all sorts and size of businesses. That is the reason they have created many tools so that MS365 works for everyone. It is all about figuring out what works the best for you and your team. You guys rightfully said that there is always a workaround for most problems within MS365. For example as a business MS can not offer all of the features in Basic Planner therefore they created Planner Premium where you have more features like Dependencies, Gantt Charts, Custom Fields etc. I also sent a response to form and my issues were similar to the person that was facing integration and feature issues with Planner vs Project. Our company requires advance features like resource management, critical path and baselines. While the features are available in Desktop Project but not "COMPLETELY" in Planner Premium and Planner Premium has collaboration and live updates features but not Project Desktop. In our company few teams use Google Workspace with Asana and they love it. I tried it and this combo felt very quick, smooth and feature packed as well. While we plan to stick with MS since it is the only company in the world, which offers a fully integrated office suite, ERP and CRM system. However we also wish Microsoft Planner Premium comes with all of the features of Project Desktop. We want to ditch Project Desktop because of lack of being cloud-first application but can not because of lack of features in Planner Premium. We are also willing to pay $50 or even $75 per user per month license for project managers for it. But Oh well, we will just wait for Microsoft to crack the Project Management side of things. P.S I love seeing the disappointment and frustration on your guys face when you are talking about the problems even though your words are polite. Really shows that you guys same the similar frustrations. Keep up the good work.

Communication charter to document all the comms, tools, when's and wheres etc so you can refer back to it as user, leader, etc and for accountability

0:04 ❤

This connects with what I tell people about approaching things from a 'role' perspective instead of a person perspective. If my user account left the system/wasn't accessible (for whatever reasons) will things continue to function? Will the next person or my teammate that's covering for me etc have what they need for things to continue? It goes along with the idea we espouse about where to go ( intranet or team/micro intranet) vs who to go to and knowledge transfer/sharing. My goal is to be replaceable (because that makes me promotable at work and the transition smooth - which applies to personal life as well, making it easier for loved ones). It's all part of the future proofing concept, and that community/relationships are more important than the individual/self/me. I understand my fleeting presence in the world and act accordingly.

Enjoyed this discussion which completely validates my M365 tool confusion! Thanks for that. Looking for the form that was mentioned but the link doesn't seem to be in the show notes above. Along those lines, the links with the ellipses (...) are broken so you might want to check on those too.

Would be more helpful if video title included "365".

What are your thoughts for a company just starting with o365 now? Should we consider making sharepoint sites or skip right to Loop workspaces for procedures and documentation?

People forget about the sunk costs/losses of knowledge when people leave. You mentioned before about teaching people where to go instead of who to go to. Building the knowledge base is important and also culture/trust related. 'if I write it down you won't need me anymore' fears.

I think your POV is related to your tagline (and how MOS has similarities with military MOS concept). You define success differently. It's about creating capacity and eliminating friction (love that analogy), freeing people up to do what you hired them to do, not downloads/copy/paste to get to a starting point on repeat. If i were a founder of a company like yours, change management/adoption would be required to take the contract.... don't offer a contract that doesn't start with the end user/employees, don't take a job that doesn't include that because who wants to spend their time building something that is not adopted, helpful, etc. Solve the real root problems not just change the hammer to a scalpel.

Yes to the origin story video!!!!!

Very insightful to hear the Bulb’s take on the updates.

Communication charter with sections for topics, structure, and process. Winwinwin