DYSARTISANIDEAS, FORGED INTO FORM.Search the episode library ↗

THE INNOVATION FORGE / Conference Insights Engine

The Query Ladder: make your Slate queries teachable

Review a Slate query through row grain, related records and reusable definitions. Use three fictional cases to find assumptions before a list becomes an action.

Conference notes organized through brass dividers into a field guide.
Make the meaning of each row teachable.

THE IDEA, IN A MINUTE

Could someone else explain this list?

The second Conference Insights Engine episode connects five Summit sessions into a learning path for query literacy, from the meaning of one row to advanced comparisons and reusable assets.

01 / THE RECORDING

Watch the episode.
Or find your moment.

Start with the person who uses the result

A counselor opens a list and sees the same student twice. Removing the second row looks like an easy cleanup. But the duplicate may represent two applications, two event registrations or an unintended relationship in the query. Until someone explains the row, the counselor cannot know whether removing it would correct an error or erase useful work.

The Query Ladder gives that conversation a place to start. In this episode, David connects five Summit sessions into his own practical learning path for Slate teams. The goal is shared understanding at the depth each role needs. A person using an approved report should be able to ask what it counts, even when someone else maintains the build.

For a first review, choose a query people already depend on. Keep the configuration unchanged while the builder and a regular user each write its purpose. Differences between those answers are useful evidence about what needs explaining.

In the recording · 04:33 ↗

Write the row sentence before fixing the count

Complete two sentences: one row represents this unit, and we chose this base because the work happens at that level. A message intended once per person has a different requirement from a checklist evaluated separately for each application. Both may involve the same student while needing different outputs.

Now compare the sentence with several records. Include someone with more than one application or event record. Ask whether each appearance in the output has a reason the user can understand. A plausible total cannot settle that question; two mistakes can leave a count looking reassuring.

Keep the row sentence beside the query. It becomes a small test for later requests. When someone adds another export, ask whether the output still means what the sentence says.

In the recording · 07:04 ↗

Give every many-row relationship a job

The subquery discussion starts with a choice that comes before configuration. When a person has several addresses, are you selecting one, counting them, checking whether any match, or collecting them for display? Those are different questions. Exporting several addresses does not establish that a filter evaluated all of them.

Use a deliberately awkward example: a current mailing address outside the target region and another address inside it. Write the expected result for an any-address question, then for a current-mailing-address question. Have the builder explain how each result follows from the relationship and selection rules.

The useful skill is recognizing when related records require an explicit treatment. Labels should preserve that treatment so a future colleague can follow the reasoning.

In the recording · 11:06 ↗

Test the audience before it becomes a message

The episode applies query literacy to an admitted-student event campaign. Attendance, registration and guest participation can describe different populations. Deposit status may belong to an application while event activity belongs to the person. The audience also changes as students act after a query runs.

Before using a list, agree on the event population, time window, application scope and status check. Include a registered non-attendee and a recent depositor in the review. Record what should happen to each. That gives the communications owner something more useful than a technical assurance that the query runs.

The same care belongs upstream of analytics. If an attended-event feature changes meaning between cycles, a chart or model inherits that change. Preserve definitions alongside the output so comparisons remain interpretable.

In the recording · 17:01 ↗

Make reuse carry its limits

A trusted pattern needs instructions for when it fits and when it does not. An attendance pattern should warn against treating it as registration. A person-based pattern should flag work that needs one row per application. Without those boundaries, copying a reliable query can create an unreliable use.

Advanced comparisons deserve particular attention. In the discussion of A Join Named Sue, a business-defined relationship needs ownership, handling for missing values and regression checks. Parameters and dictionary exports also need maintainers who understand where their outputs are used. Reuse brings a responsibility to keep the explanation with the logic.

In the recording · 23:49 ↗

Turn one review into a training artifact

Finish by asking someone who did not build the query to explain its purpose, row grain, related records and exclusions. Let that explanation show where the documentation needs work. Keep the exercise within existing access controls; people can learn from approved examples without receiving broader access to sensitive bases.

Choose one improvement small enough to complete: clarify a join label, document a selection rule or add an edge case to the review. Name who will maintain it. The next time this query is copied, changed or handed over, the team should inherit a reasoned decision rather than another puzzle.

In the recording · 26:37 ↗

03 / A SMALL EXPERIMENT

Review three queries before changing them

Use these fictional cases to practice the Query Ladder. For each, write the row sentence, name the ambiguity and specify a record whose expected result would test the logic.

One student, two applications

A counselor needs one follow-up row per student. A fictional list contains two rows for someone with two active applications. What must the team settle before deduplicating?

Compare your reasoning

Confirm that the action is person-based, then define how applications qualify the person and which application details the counselor needs. Test a person with one qualifying and one nonqualifying application. Removing a duplicate is not a substitute for deciding the intended grain.

Revisit this moment · 08:04 ↗
The address that disappears

A fictional regional list exports several addresses but only checks the rank-one address. One student has an in-region address that is not rank one. Should that student appear?

Compare your reasoning

Answer separately for any address in the region and current mailing address in the region. Document the intended relationship, selection and eligibility conditions. Use the same record to verify both expectations; decide whether a related-row existence test fits the actual question.

Revisit this moment · 11:06 ↗
The audience changes overnight

A fictional event follow-up query ran yesterday. One student registered but did not attend; another attended and deposited this morning. The message is intended for attendees who have not deposited. What should the review check?

Compare your reasoning

Define attendance and the relevant event population, confirm how person and application records connect, and specify how current deposit status is checked before action. Under the stated definitions the non-attendee should not qualify, and the recent depositor should be excluded once the current status is evaluated.

Revisit this moment · 17:01 ↗
Build a test card to take with you

Notes stay in this tab. Reloading clears them.

04 / INSIDE THE STUDIO

The seams are part
of the story.

Behind the episode

David introduces five Summit sessions and says his goal is to connect them into a practical learning path. Near the close, he returns to a suggested study order, moving from tables and row grain through subqueries to advanced comparisons and reusable techniques. The recording builds a teaching sequence rather than recreating a configuration walkthrough.

Revisit the studio moment · 02:36 ↗

Art from the workshop

Conference Insights Engine series artwork, turning a collection of notes into a guide for practice.

Open the artwork ↗

KEEP THE IDEA MOVING

Where would you take it next?

CONTINUE EXPLORING