How user collaboration shapes product direction
How do we decide what to build next in pForecast? By working closely with the people who use it.
Recently, members of the pForecast Product Committee met in Bergen to discuss priorities, share experiences, and acquire about future development. The committee brings together users and product representatives to ensure that development is guided by real-world needs, not assumptions.
How do we decide what to build next in pForecast?
By staying close to the people who use it. The pForecast Product Committee recently met in Bergen to review priorities, exchange user insights, and shape the direction of future development. The committee brings together users and product representatives to ensure the roadmap reflects real operational needs rather than assumptions.
What is the pForecast Product Committee?
The Product Committee is a forum where selected users and the pForecast team meet to:
- Share feedback from ongoing projects and workflows
- Discuss challenges and emerging needs in forecasting and reporting
- Align on product priorities and future development
This ensures that pForecast evolves in line with how companies work — particularly in complex areas like production forecasting, uncertainty analysis, and reporting processes such as RNB.
The committee plays a key role in:
- Providing strategic direction for product evolution
- Prioritizing initiatives based on user value and impact
- Ensuring alignment between product development, customer needs, and market requirements
Why user involvement matters
Forecasting workflows are rarely static. They evolve with:
- New data sources
- Changing regulatory requirements
- Increasing expectations for transparency and auditability
By involving users directly in product discussions, pForecast development is grounded in:
- Practical use cases across assets and organizations
- Real challenges in day-to-day forecasting work
- Continuous validation of what creates value
This reduces the gap between product functionality and operational reality.
From feedback to product development
Input from the Product Committee is actively used to guide development priorities. Rather than relying solely on internal roadmaps, pForecast follows a model where:
- User feedback is continuously incorporated
- Priorities are discussed and validated with customers
- Development decisions are anchored in real operational needs
This approach helps ensure that new features are not only technically sound—but also relevant, usable, and impactful in practice.
Built in collaboration
The meeting in Bergen is an example of how pForecast is developed in close collaboration with its users. This way of working supports:
- Better alignment between product capabilities and user needs
- Faster adoption of new functionality
- Greater confidence in how the platform supports critical workflows
Developing forecasting software is not just about adding features — it is about understanding how those features are used in real-world processes. The pForecast Product Committee is a key part of ensuring that development stays aligned with that reality.
Want to learn more?
Curious how pForecast works in practice?
Connect with our Product Manager for a short walk-through of how pForecast supports continuous, uncertainty-aware forecasting and reporting workflows.