Leap Session Q&A: Can We Do That? Beyond Internal Work Management

What a great session - tying the technical nitty gritty to the overall value add for your clients! I'm so impressed with how you differentiated your role in your company by thinking bigger!

I am especially interested in the custom statuses you created for each stakeholder. Can you give some examples of the different statuses you used for each stakeholder?

Sure @Kyna Baker - inactive‚ we used custom statuses in setting up the intake and execution approval processes.

During intake, the queue routes proposals to the default stakeholders and their approval is triggered by 'New' status. If the marketing proposal includes an Enablement activity, for instance, our Program Manager selects the custom status 'Enablement Review' to trigger the approval path for that stakeholder. Basically, we tied the custom statuses to a path on the approval process to provide visibility to the right stakeholders at the right time.

We also used a 'Response Required' custom status and Updates as reporting fields to flag rejections. Because the majority of users are Requesters and work from custom dashboards, this was an easy way to communicate when and what action is needed.

This was something we needed to work around to accommodate their licensing/access restrictions. The requestors open the issue (for proposal) or task (for POP delivery) that was rejected and message the Program Manager with questions or to confirm the requested corrections are in place. She has the license/access to update the status and re-trigger the approval process for them.