Learn about how different roles can leverage the primary capabilities Productable provides users with to comprehensively and efficiently manage a portfolio of new and developing Projects.
Definition of Productable roles:
- Org Admin: admins are Productable staff who manage the organization
- Org Owner: owners approve org access requests and have permissions across all portfolios
- Org Member (i.e. View-Only Member): can view all activity across all Collections and Portfolios but cannot create, update or delete anything
- Collection Owner: can manage everything in the Collection and all Portfolios and Projects within it
- Portfolio Owner: can manage everything in the Sand all projects within in
- Project Member: can manage updates on the project
Portfolio set-up:
These capabilities allow organization and portfolio leaders to prepare the platform before your teams join Productable. Doing this meticulously before creating Projects and onboarding Project teams is critical.
| Function | Description | Permitted Roles | Tutorial |
| Setting stages and Decision Criteria | Customizing the Stages of innovation maturity and all Decision Criteria in each stage |
|
Link→ |
| Setting custom Portfolio fields | Enabling custom required and optional fields that are visible in each Portfolio |
|
N/A |
| Setting custom Sub-portfolio fields | Enabling custom required and optional fields that are visible in each Sub-portfolio |
|
N/A |
| Setting custom Project fields | Enabling custom required and optional fields that are visible in each Project and on the Sub-portfolio and Portfolio projects tab |
|
N/A |
Inviting your team
Once the platform is ready, the below capabilities will allow Organization, Portfolio, and Sub-portfolio leaders the ability to create Projects and invite team members.
| Function | Description | Permitted Roles | Tutorial |
| Creating Projects |
Add new Projects, either individually or in bulk, to a Sub-portfolio Upload any relevant files, and add Project Members |
|
Link--> |
| Managing Collection Owners |
Adding and removing team members to Collections Collections Owners can only add new members to their Collection |
|
Link--> |
| Managing Portfoio Owners |
Adding and removing team members to Portfolios Collection and Portfolio Owners can only add new members to their Portfolios. |
|
Link→ |
| Managing Project Members |
Adding and removing team members to individual projects Project Members can only add new members to their Project |
|
Link--> |
| Inviting Org Members (View-Only Members) | The ability to invite individuals in a View-Only capacity |
|
Link→ |
| Managing Org members | The ability to remove Org Members (View-Only Members) |
|
Link--> |
Portfolio management
Once team members are in Productable, Projects are created and up-to-date, Project Members will begin the work of innovating and leaders can begin managing the Collection/Portfolio.
| Function | Description | Permitted Roles | Tutorial |
| Making decisions on Stage Change Requests | The ability to progress Projects to the requested next stage, off-ramp a project, or request more information from a Project team |
|
Link→ |
| Updating Portfolio Funding | Indicating available and unavailable funding within a Portfolio |
|
Link→ |
| Update Portfolio Outcome | Indicating a target outcome within a Portfolio |
|
Link-> |
| Commander's intent/problems to be solved | Indicating focus areas of the Collection/Portfolio, influenced by commander's intent |
|
Link→ |
Project support [Portfolio Activity tab]
The Activity tab in a Portfolio is where users will find Wins, Barriers, Insights, and Progress Updates from teams. Here teams can collaborate on blockers or gain clarity on progress made. If integrators need leader awareness, they can escalate activity up to the Portfolio level.
| Function | Description | Permitted Roles | Tutorial |
| Resolving Barriers |
Indicating that a Barrier has been resolved and no longer needs attention Doing so reduces the number of outstanding Barriers within a Portfolio |
|
Link-> |
| Escalating Barriers; promoting Wins, Progress Updates, and Insights | When Barriers are difficult to address at the Portfolio level, they can be escalated up the chain so they are visible at the Collection level |
|
Link-> |
| Comments and @mentions | You can have conversations on any post and @mention active users in Productable to collaborate |
|
Link-> |
Project review [Projects tab]
In a Collection or Portfolio, the Projects tab will display a comprehensive account of status across all active and idle projects. Use custom filters and sorting capabilities to view the data however you'd like.
| Function | Description | Permitted Roles | Tutorial |
| Filtering | Use flexible filters, groupings, and sorting functionality to view Project activity in a Portfolio and/or Collection |
|
Link-> |
| Setting activity color thresholds |
The "Last active" column shows red/yellow/green status indicators. These colors are set based on whether a Collection Owner wishes to set aggressive, moderate, or conservative expectations for Project activity |
|
Link-> |
| Nudging Project Members for a progress update |
Waiting for a Progress Update from a Project team? Nudge them for an update and they will receive a notification prompting action |
|
Link-> |
| Moving Projects and forcing Stage Changes |
In certain circumstances, Projects need to be moved between Stages without going through the typical innovation maturity Projects sometimes need to be moved to different Collections or Portfolios too |
|
N/A |
Individual Project page [Stage Report + Activity tab]
The individual Project page is where progress is made for a project team. A project team's activity rolls-up to the Portfolio and Collection level.
| Function | Description | Permitted Roles | Tutorial |
| Submitting Decision Criteria data | This is where Project Members report data, findings, evidence, and learnings to answer the Decision Criteria questions, giving integrators and leaders the confidence to further invest in a Project |
|
Link→ |
| Reporting Barriers | If a Project team is facing a blocker, pain, or bottleneck, report what's happening so integrators and leaders are aware and can help |
|
Link-> |
| Posting Wins |
Milestones are worth celebrating and are likely shared with leadership Post a Win and tag any team members who helped you make progress |
|
Link-> |
| Posting Progress Updates | Working to develop the solution and reporting the data in the Stage report is priority #1 for a Project Member, but sometimes a team just needs to give leaders a general update on what's going on |
|
Link-> |
| Sharing Insights |
Learn something interesting from any facet of developing your solution? Posting an Insight is a great way to share the knowledge with your organization |
|
Link-> |