How might Hexagon PPM enhance the mobile capabilities of its EcoSys Enterprise Project Performance software for better on-site project management?

Introduction

To enhance the mobile capabilities of Hexagon PPM's EcoSys Enterprise Project Performance software for better on-site project management, we need to focus on improving user experience, functionality, and data accessibility in mobile environments. I'll outline a strategic approach to address this challenge, considering user needs, technical constraints, and business objectives.

Step 1

Clarifying Questions

• Looking at the product context, I'm thinking EcoSys might be used by various roles in project management. Could you help me understand who the primary users are for the mobile version, and what their key use cases might be?

Why it matters: Determines which features to prioritize for mobile optimization Expected answer: On-site project managers and field engineers are primary users Impact on approach: Would focus on real-time data entry and visualization features

• Considering user behavior, I'm curious about the current mobile usage patterns. What percentage of EcoSys users are currently accessing the software via mobile devices, and how does their usage differ from desktop users?

Why it matters: Helps identify the potential impact and adoption rate of mobile enhancements Expected answer: 30% mobile usage, primarily for quick updates and data viewing Impact on approach: Would prioritize speed and ease of use for common mobile tasks

• Regarding pain points, I'm wondering about the specific challenges users face with the current mobile version. What are the top complaints or feature requests from mobile users?

Why it matters: Directly informs which areas need the most improvement Expected answer: Slow load times, difficulty inputting data, limited offline functionality Impact on approach: Would focus on performance optimization and offline capabilities

• Thinking about the product lifecycle, where does EcoSys stand in terms of mobile development? Is this an initial mobile rollout, or are we iterating on an existing mobile version?

Why it matters: Determines whether we're building from scratch or refining existing features Expected answer: Existing basic mobile version, looking for significant enhancements Impact on approach: Would focus on iterative improvements and new feature additions