What improvements could Cincom Systems make to its Eloquence document automation system to increase user adoption and efficiency?

Introduction

To improve Cincom Systems' Eloquence document automation system and increase user adoption and efficiency, we need to conduct a comprehensive analysis of the current product, user needs, and market dynamics. I'll approach this challenge by examining key stakeholders, identifying pain points, generating innovative solutions, and proposing a strategic implementation plan.

Step 1

Clarifying Questions (5 mins)

• Looking at the product context, I'm thinking Eloquence might be targeting mid to large-sized enterprises with complex document needs. Could you confirm the primary user base and their typical use cases?

Why it matters: Determines the scope and complexity of solutions we should consider. Expected answer: Mid to large enterprises in regulated industries like finance or healthcare. Impact on approach: Would focus on compliance features and scalability if confirmed.

• Considering user behavior, I'm curious about the current adoption rates and usage patterns. Can you share any data on user engagement metrics, such as daily active users or time spent in the system?

Why it matters: Helps identify whether the issue is initial adoption or sustained usage. Expected answer: Moderate initial adoption but drop-off in long-term usage. Impact on approach: Would prioritize onboarding improvements and sticky features if confirmed.

• Regarding pain points and market position, how does Eloquence currently compare to competitors in terms of feature set and user satisfaction?

Why it matters: Identifies areas where we can differentiate or need to catch up. Expected answer: Strong in automation but lagging in user interface and integration capabilities. Impact on approach: Would focus on UI/UX improvements and expanding integration options if confirmed.

• Considering the product lifecycle, where is Eloquence currently positioned, and what are the key growth objectives for the next 12-18 months?

Why it matters: Aligns our improvements with the overall product strategy. Expected answer: Mature product looking to expand market share and modernize offerings. Impact on approach: Would balance quick wins with longer-term platform modernization if confirmed.