DYSARTISANIDEAS, FORGED INTO FORM.Search the episode library ↗

THE INNOVATION FORGE / Conference Insights Engine

Build decision infrastructure for your Slate work

Use five questions to connect a Slate build to its decision, owner, evidence, action and review, with a practical test for dashboards, sources and signals.

Conference notes organized through brass dividers into a field guide.
Give the evidence an owner and a next step.

THE IDEA, IN A MINUTE

Start with the choice the work should improve.

The first Conference Insights Engine episode connects change management, Querybase Views, yield volatility and origin sources through a five-question review of the decisions a Slate build supports.

01 / THE RECORDING

Watch the episode.
Or find your moment.

Give the build a decision sentence

A dashboard can have a dependable refresh, carefully chosen colors and a loyal audience while leaving its purpose unresolved. Ask three people what they should do after reading it. If their answers differ, adding another chart is unlikely to settle the question.

The opening Conference Insights Engine episode offers a practical review standard for Slate work: identify the decision, its owner, the evidence, the action and the way the result will be assessed. David develops this as his synthesis across conference sessions on change, Querybase Views, yield volatility and origin sources. The framework connects those subjects without treating every local example as a universal prescription.

Start with one object people already use. Finish the sentence, “This build helps us decide…” Use a choice rather than a topic: which admitted students need follow-up this week is more useful than student engagement. The sentence gives the next design conversation a boundary.

In the recording · 17:52 ↗

Separate maintaining the object from owning the choice

The person who maintains a query may have no authority to decide how its results should guide staff work. The episode separates technical ownership from decision ownership for exactly this reason. A working report can outlast the practice it was meant to support.

Write down both roles. Then ask who can change the action rule, who resolves an ambiguous case and where the reasoning will be kept. For a recurring vendor review, that reasoning might include the original use case and the basis for the last renewal. A successor should be able to reconstruct the choice without finding the person who made it.

In the recording · 18:58 ↗

Choose evidence that answers the actual question

The origin-source discussion provides a useful boundary: the initial hand raise and the full recruitment journey are different analytical questions. A single field cannot reliably explain first entry, subsequent influence and the contribution of every campaign. Define what the field represents before making an investment decision from it.

The same discipline applies to a counselor list. Recent event attendance, application stage and a missing deposit may support a review queue. They do not establish why someone has not deposited. Keep the observable evidence separate from the explanation staff still need to learn.

For Querybase Views, the episode asks whether repeated calculations are expensive, whether a defined population needs guardrails and whether scheduled lag is acceptable. These are design questions to resolve locally. A faster result is useful only if its scope and freshness still fit the decision.

In the recording · 19:54 ↗

Make the response visible

A score or dashboard becomes easier to use when the next step is explicit. The episode illustrates this with an admitted student who attended a high-intent event but has not deposited: a possible response is counselor follow-up within three business days. That is an example to assess against local practice, not a demonstrated outcome or an automatic rule for every student.

Try writing the response in four parts: when this evidence appears, this role reviews it, within this period, using this process. Include exceptions. A student who has already received help should not get duplicate outreach merely because yesterday’s list still contains the record.

Apply the same test to maintenance work. An unmapped source belongs in a governance queue with an owner. A contract nearing renewal needs a review window. Naming the queue without naming who acts still leaves the work unfinished.

In the recording · 21:18 ↗

Measure use without inventing impact

Decide what improvement would look like before the next review. A reporting change might reduce manual preparation or make a weekly meeting more useful. A view might reduce query errors. Source cleanup might reduce unmapped values and clarify conversion reporting. Those are concrete results worth checking.

The recording also cautions against treating every improvement as causal. A deposit increase following a campaign does not, by itself, prove the campaign caused it. Record what changed, who was included, what comparison is available and what remains uncertain. Operational usefulness and causal evidence answer different questions; both deserve accurate descriptions.

In the recording · 22:38 ↗

Leave the next owner a reviewable tool

Keep the first pass small enough to finish. Choose one build, write its decision sentence, name the owners, define an action rule and put a review date on the calendar. Preserve the explanation alongside the object so the next person can understand more than its configuration.

At the review, compare intended use with actual use. Was the evidence timely? Did someone act? Did the action help resolve the question? If the answers expose a gap, revise the definition, the workflow or the evidence before adding features. The useful outcome is a tool whose purpose can be explained, questioned and improved.

In the recording · 25:24 ↗

03 / A SMALL EXPERIMENT

Put one decision under review

Work through these fictional cases, then apply the five-question test to one real build. Identify the decision, decision owner, evidence, action and review measure.

The popular dashboard

A fictional team opens a dashboard every Monday, but each person gives a different answer about what it helps them decide. What should the team settle before requesting another chart?

Compare your reasoning

Write individual decision sentences and compare them. Agree on one decision, distinguish the technical and decision owners, and specify the action the evidence should inform. Use the next review to check whether that decision actually happens.

Revisit this moment · 17:52 ↗
The overloaded origin field

A fictional report treats the first inquiry source as proof that the same channel caused the eventual deposit. Which claim can the field support, and what needs a different design?

Compare your reasoning

The origin field can describe the recorded initial hand raise under its documented definition. Full-journey influence and causal channel impact need additional evidence and appropriate methods. Review entry paths, unmapped values and the investment question before drawing conclusions.

Revisit this moment · 09:58 ↗
The fast weekly view

A fictional counselor team uses a weekly refreshed view for daily follow-up. It loads quickly, but a student who deposited yesterday still appears. What needs to be agreed before using it as an action list?

Compare your reasoning

Specify the freshness required by the decision, make the refresh timing visible and define how staff check current status before acting. Name the owner and exception process, then review whether the list reduces work without creating duplicate or outdated outreach.

Revisit this moment · 28:13 ↗
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

Early in the recording, David identifies decision infrastructure as his interpretation across several Summit sessions. He then returns to those sessions near the close with different study questions for each. The episode is organized as a cross-session argument rather than a configuration walkthrough.

Revisit the studio moment · 02:08 ↗

Closing song

Hear the closing song in the full episode.

Hear the song in the episode

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