![]() ![]() ![]() When it comes to knowledge management it can even be more important to standardize tool usage. People do not have to learn how things work when they interact with other teams or domains. Because with standardization it becomes very predictable how things work. But it can also actually benefit usability. Standardization can help in areas such as cross-team collaboration and portfolio insight. On the other hand, large organizations need to have some level of alignment. On one hand you want to give teams as much autonomy as possible, so that they can learn what works best for them. Hi Land, this is a great question! One of the big dilemma's large organizations often face is the 'autonomy versus alignment challenge'. Having a sort of pipeline of tools example in place to show the various processes from start to end and back will make people understand not only how to use the tools but also why we use them and may make them more enthusiastic about the tools in place, which in turn could create higher levels of productivity and satisfaction. ![]() Spending some more time for each employee starting new or working longer already but wanting to know more about the tools and the interoperability of them will pay itself back imho. Currently our on-boarding process does not include this and I think that is a missed opportunity. The thing I am currently still missing is training material focusing on other such tools and possible integrations and a mandate from management to make this a standard (mandatory) on-boarding continuation. In the advanced part I highlight the many other possibilities and the integration with our Confluence and use of add-ons to expand into other tools and possible overlap.įor Confluence I made a similar training, with the same basic and advanced parts. It is possible to create trainings that highlight the use of individual tools and during this show the bridging between other tools and gradually move on to the next tool.įor example, I have created a Jira training which consists of a basic and advanced part where I first focus on getting people trained on the basic information about Jira and why we use it and then gradually explain how to use the interface and many of its (basic) features. I think the short answer is: there is no best way.īecause each company has their own unique setup it will require a unique approach each time as well to deal with things like this.ĭecisions should be made by a group of people who are able to see the big picture and can make clever choices to select which tools are the starting point, which restrictions you may want to impose on changes / additions, what terms and tools should be leading and document this somewhere clearly and have it available readily and use it as training material (reference). Hi, this sounds very familiar to our organization's situation where we also have overlap with multiple systems with like capabilities and integration with systems/services that also have similar features. What's the best approach to take to train users to use an ecosystem of tools (Jira, Confluence, and a suite of integrated tools) for what they're best at? Sometimes, having too much choice is frustrating. Integrating organizational tools with Jira and Confluence allows for synergies and an expansion of capabilities, while reducing error however, when teams can complete like activities (such as tracking requirements or updating status) in multiple tools, training users on effective usage of the tools becomes gray and muddy. From an organizational standpoint, standardization and governance can provide efficiencies, clarity of purpose, and a better user experience for novices. When working with an ecosystem of integrated tools, with some considerable overlap of functions/capabilities across them, what is the best way to effectively train users to leverage them together at scale?įlexibility is good for the user experience of intermediate and expert users, but it comes at the cost of complexity and risk at scale. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |