Congratulations 🎉 You're the proud Owner of a Business Case 🙌 So, what next?
What are their responsibilities?
What is an Owner? 💭
Selected from the Active Directory via a people picker, an Owner can be one or more people. These users will be displayed on the card of the record and are ultimately responsible for the business case. The right to be an Owner must be granted by an Admin at the template level. More on adding users to a template here!
What are their responsibilities? 💌
So we know what an Owner is, now it's time to understand what they should be looking after!
- Creating records. Adding new Business Cases and inputting the initial data.
- Delegating pieces of data. Assigning other users as owners of a particular risks, or as resource on a specific task. Even if these users can't access the record, they can look after their elements through the personal page.
- Maintaining the data. Admins and Owners are the only people who can edit an entire record. So it's up to them to upkeep it's contents, from timelines to updates, keep it fresh!
- Submitting stage change requests. An Owner can submit a record to change stage, but approval for stage change is granted by Process Manager.
What should their habits be? 🗓️
Besides living their best lives and fulfilling their wildest dreams, here are the best Owner habits!
Ongoing ☀️- RAID elements such as risks and issues should be entered by the Owner as soon as they occur, hopefully this isn't often, but could be on a daily basis!
- Weekly/ Monthly 🌳
- Polish up any periodic tables, you may choose to track financials like estimated costs or benefits on a week-by-week or month-by-month basis.
- Monthly 🍃
- Ask yourself "Is this right?" if big change is needed, consider creating a version to capture the record before big changes are made.
- Check over the details for reporting purposes, no Owner wants to be exposed in a monthly update meeting for having wonky records!
- Quarterly 🍂
-
- Audit your activity, if you haven't look at a record over the last quarter, does it need to be repurposed or killed? Don't let redundant records clog your app!