Productivity Management
When an application employees are using hasn't yet been marked productive in the system, they can request to flag it as productive from their manager. Approvals can also be granted only for a specific time window.
The problem
No system can know in advance whether every application is productive. A visual tool a design team lives in may be a distraction in another department. Berqun leaves that judgement to you and moves the process inside the system.
How it works
- An employee using an application that has not yet been classified sends a request to their manager to mark it productive
- The manager approves or rejects the request
- Approval can also be granted for one specific time window only
- A productive activity can later be made unproductive, and vice versa
- Activity management rules let you classify in bulk rather than one by one
Why it directly affects the score
Pending requests count as unproductive time until a manager decides. Keeping that queue clear is therefore necessary for BQ scores to reflect reality. It is the single most common reason scores look low on a new deployment.
Frequently asked questions
Can approval be temporary?
Yes. You can treat an application as productive only for a specific time window; outside that range its previous classification applies.
Can I change a classification later?
Yes. There are separate flows for making a productive activity unproductive and the reverse, and the change is reflected in the relevant period's scores.
Do I have to classify every application individually?
No. Activity management rules let you define general rules and classify similar activities together.