WorkshopIQ FAQs

No, not at all. Workshops can be used as ongoing or time-boxed events dependent on the use case. We built this product with the goal of collecting and interacting with idea/lesson repositories and helping teams focus on continuous improvement, but have a place to go in order to do so.

Although continuous improvement is focused on these issue types, it need not be restrictive. In fact, we see use cases implemented where users leverage workshops to manage Risk Repositories and time-boxed brainstorming events.

Product discovery, Lessons Learned (PMO or project specific), Pain Points, and Feedback are all common issue types used.

WorkshopIQ will create 3 issue types when installed, namely:
    i. Lessons Learned
    ii. Ideas
    iii. Risks

There is no limitation to how you use the product and issue types – feel free to be creative and experiment. The engine of this product is Jira Software, so the same concepts apply from an issue type perspective. You can feel confident that the product is scalable and robust. Software, so the same concepts apply from an issue-type perspective. You can feel confident that the product is scalable and robust.

We have implemented a keyword-drive approach as a starting point (you can expect some progressive changes in this functionality). This means that we use a keyword matching approach that reviews the connected workshops and finds the best matching workshop entries, and presents those back to users.