Considerations to keep front of mind:
- Do you have an approach that considers different levels of work (e.g. strategy vs. execution - both of which can be broken down further)?
- Always bear in mind that different organization levels often have different technology capabilities.
- Not only that, the frequency of use should also guide the friction of flow.
- Highly aggregated processes reduce friction, which can help users and teams navigate more freely.
- What is your goal? Building a Portfolio and Program Management approach is very different to mimicking a unique use case.
- Jira scalability and administration overhead should play a part in decision making. Early adoption of this mindset will help reduce future maintenance costs.
What We Think
There is no right or wrong in this case, but organizations that rethink and challenge complexity are those that are most successful in taking charge of their business processes. Try modifying your Jira workflows to suit your organization, and if you need help, contact us for help.
