Thinking article · Cross-team practice

Your Users Don't Care How Your Teams Are Organized

How shared requirements changed my Report Builder design, and where we deliberately kept differences.

The most useful result of our cross-team Report Builder work was a change to my own design: selecting output columns and defining filters needed distinct workflows. The attributes users wanted to see were not always the ones they needed to filter by.

Share the model. Respect the task.

At athenahealth, I brought my Report Builder foundation into an existing alignment effort across product lines: configuration on the left, active selections in the main workspace. The foundation was my design, and I drove the effort to standardise its components; the alignment sessions were run jointly with a designer from an adjacent product line.

We kept that foundation recognizable while preserving three differences:

  • Boolean filtering for complex conditions.
  • Hierarchical selection for a domain-specific taxonomy.
  • Entry points suited to each product’s workflow.

These differences followed from user tasks. Making every control identical would have hidden requirements rather than resolved them.

Let other teams change your design

The other designer and I worked through detailed decisions together, then brought the direction to the wider group. Adjacent requirements exposed the weakness in my combined columns-and-filters model. Separating those activities improved the shared foundation.

The useful alignment question became: what should users recognize, and what needs to differ?

What carried forward

Report Builder went through RITE usability testing, and its interaction direction carried into implementation on a newer analytics platform. We did not measure cross-product learning or establish adoption of every shared pattern.

For the next collaboration, I would ask:

  • Are these the same user concepts, or just similar-looking controls?
  • Which differences come from the task, and which come from history?
  • Can users transfer what they learned between the experiences?

Related: Report Builder case study.