Understand the responsibility
Ask what was actually designed or implemented, which dependencies were outside scope and who owns the operating process. A clear boundary makes the work easier to assess.
ENGINEERING IN FOCUS
The work behind the software.
Explore the business problems, scope decisions and engineering thinking behind our product portfolio.
Community product engineering
Connecting the community record.
Households, members, collections and reviewed handovers in one administrative context.
Read the overview
Commerce product engineering
Following stock through the business.
Connecting the counter, catalogue, purchasing, inventory and operational financial records.
Read the overview
Governance product engineering
A workspace with organizational context.
A committee-focused product direction with a distinct workspace for each organization.
Read the overviewHOW TO REVIEW THE WORK
Look closer at the engineering.
The most useful way to evaluate software work is to examine the decisions behind it. Our product engineering overviews describe the business context, current scope and design choices in Community, Commerce and Governance. They are a starting point for a technical conversation rather than a substitute for a current product demonstration.
Review the difficult path
Look at a correction, a permission change, a failed integration or a data migration discrepancy. The handling of exceptions often reveals more than the ideal journey.
Connect evidence to the claim
Match the statement to a working build, design decision or acceptance record. Measured outcomes need a baseline, observation period and attribution; a visual concept is not deployment evidence.
Bring a relevant scenario to a project or product review. We can use it to discuss requirements, architecture choices, current functionality and the evidence needed for your next decision.