Exxat · DS Patterns · v0.3.0

— Why the product feels the way it does.

Built around the people using it.

Three kinds of people open our products — admins, faculty, and students. They want different things, at different speeds, with very different comfort around screens full of data. These are the patterns that let one product serve all three — without anyone feeling rushed, lost, or in over their head.

I · Answer first

Show what changed,
then show the rows.

Open a list — placements, rotations, sites, students — and you don't land on a wall of records. You land on the answer: what's working, what's slipping, what's new this week. The records are still there, one scroll down. But the question — "is anything wrong?" — gets answered before you have to ask it.

First glance · The summary band
Active placements 1,247 +18 this week
Completed 412 +24 this week
Pending review 23 5 over 30 days
Compliance rate 94% steady
Second glance · The records below
Maya Chen — Boston General PLC-2026-018 Active
Priya Iyer — Mass Eye & Ear PLC-2026-019 Review
Daniel Park — Children's Hospital PLC-2026-020 Active
Aiyana Brooks — UMass Memorial PLC-2026-021 Overdue

II · Many shapes

Same data,
told a different way.

A table is the right answer when you're comparing fifty placements side by side. A board is the right answer when you're triaging this week's reviews. A folder is the right answer when you're a student looking for the one site you're going to. Same records, six shapes — and the filters never lie to you, because every shape reads from the same list.

Table

Dense, sortable, comparable. The right shape when you're slicing fifty records by status, site, or week.

Best for · admin

List

One record per row, room to breathe. Status and the two facts you actually need — nothing more.

Best for · faculty

Board

Cards in columns, grouped by status (or any field you choose). The right shape when you're moving work along.

Best for · faculty

Dashboard

Charts, KPIs, and the records summarized. The right shape for the weekly meeting, the steering review, the trend question.

Best for · admin

Folder

Big tiles, room to scan. The right shape for browse-and-pick — students looking for their site, faculty browsing sites by region.

Best for · student

Tree & details

Hierarchy on the left, the chosen record on the right. The right shape for nested data — programs inside cohorts, sites inside networks.

Best for · admin · faculty

III · Quiet by default

Powerful,
not loud.

Most people will never reorder a column. Most won't write a filter. Most won't paint a conditional rule that says "highlight overdue reviews in red". But some will — and they should be able to without us shouting "advanced settings!" at everyone else. The basics stay visible. The deeper controls hide behind one button on every hub.

Default · What everyone sees

The hub, plain and unflinching.

KPIs at the top. Records below. A search box, a few status chips, and the most useful columns already chosen for you. You can do real work without changing a single setting.

  • Sensible columns picked for the role
  • One-click search, no syntax
  • Status visible as chips, not codes
  • The right view selected by default
On request · Open Properties

Everything else, behind one button.

The Properties drawer is where the power lives — filters, sort rules, hidden columns, conditional formatting, the lot. It's one button on the toolbar. It doesn't open unless you ask it to.

  • Filters with and / or connectors
  • Multi-column sort rules
  • Column visibility & order
  • Conditional rules — paint your own answers
  • Density, gridlines, pagination

IV · Three audiences

One product,
three speeds.

We don't ship three different apps. We ship one — and let it meet each person where they are. Same buttons, same data, same rules — but defaults, density, and the order things appear in are chosen so each role opens the screen and feels at home.

Admin

The power user.

Lives in the product all day. Wants to slice every dimension — by year, by site, by cohort, by status. Saves views, paints rules, exports to CSV when something has to leave the building. We don't get in the way.

  • Full Properties drawer
  • Conditional rules, saved views
  • CSV & PDF export
  • Table view by default
Faculty

The time-constrained reviewer.

Opens the product between classes. Wants the system to anticipate — "what needs my attention today?". Reads at a glance, acts in one click. No setup, no jargon. Defaults are the experience.

  • KPI-first hub layout
  • Status chips, plain language
  • List or board view, not table
  • Sensible defaults, no setup
Student

The occasional visitor.

Logs in once a week to check on their placement, find their site, or pick up an update. Wants a clean, calm screen — no walls of data, no "advanced" anything. Folder view, big search, the answer in two clicks.

  • Folder view first
  • Big, dedicated search
  • Plain language, no codes
  • Power features hidden, not removed

V · Yours when you ask

Power,
when you ask.

Some users will never customise anything. Some will spend an hour tuning a board until it's exactly the way they think. Both are right. The defaults are real defaults — they work for the first session and the hundredth. When you do tune something, it stays tuned — for you, per tab, quietly. Nobody pays a cost for choices they didn't make.

i

Defaults are the experience.

We pick the columns, the view, the density, and the sort order so the first session works without any setup. If you never open Properties, the product still does its job.

ii

Customisation is layered, never required.

Every advanced control — filter rules, conditional formatting, column visibility, board grouping — lives behind one consistent door. If you don't need it, you'll never see it.

iii

Your changes stick.

Switch a view, save a filter, hide a column — it stays that way next time you come back. Per user, per tab. No re-tuning every Monday.

iv

Names speak English.

We use words people use. "Overdue", not OVRD_30. "Pending review", not STATE_2. The system speaks like a colleague, not a database.