Start with a question you can test
At Slate Summit 2025, seven Quick Strikes interviews return to a familiar problem: knowing enough to be responsible for a system while still having plenty to learn. Annie Lehwald describes the jolt of meeting a room full of experienced builders. Her advice is to recognize both strengths and gaps, then learn from the people around you.
Give uncertainty a specific shape. Name the task, explain what you expected and identify the step you cannot yet account for. Annie describes using Slate AI for questions she hesitated to ask people. Treat an answer as a starting point: check the documentation, try a fictional example and bring unresolved questions to a colleague.
In the recording · 02:45 ↗Define a useful first release
Ben Parsons describes the pressure to anticipate every possible use case before letting anyone try a tool. His alternative is a useful version that covers most of the work, followed by feedback and adjustments. The purpose of starting smaller is to make learning possible while the project can still change.
Write down the ordinary case the first version will handle and the exceptions it will send to a named person. Ben's 80-to-85-percent example is a way of resisting perfectionism, not a universal release threshold. A missing convenience and an incorrect access rule carry different consequences. Test essential behavior, explain the limits and agree on a review point before expanding the scope.
In the recording · 05:38 ↗Put the information beside the decision
David Garzon wanted counselors to use recruitment data without repeatedly requesting queries and reconciling spreadsheets. He describes bringing applicants, admitted students, enrolled students and their associated schools together geographically in Voyager. That gave counselors a more approachable way to consider travel and engagement.
Choose one decision before arranging a view. A counselor planning visits needs to understand what each count represents and which period it covers. Use consistent definitions, show the comparison clearly and ask someone unfamiliar with the build to explain what they would do next. Track whether staff can find, explain and use the information before trying to connect the new view to a change in enrollment outcomes.
In the recording · 08:19 ↗Document the choices as well as the clicks
Paloma Barragan names Scribe as a helpful companion for showing new users how to work in Slate. Her examples include creating events and preparing Deliver communications, with screenshots, notes, templates and internal naming conventions. Those details make a recurring task easier to repeat across people.
Create a guide around one complete task. Include its purpose, starting conditions, required template and a visible check for success. Use fictional information in screenshots and have a new learner follow the guide without the author directing every move. If they can copy the clicks but cannot choose the right template, add the missing decision. Give the guide an owner and revisit it when the process changes.
In the recording · 10:42 ↗Make partnership part of the working day
Tommy Kroll connects being a good data partner with being present. He teaches onboarding, welcomes ideas, meets with colleagues and joins the everyday work of the office. Being available helps people bring forward the problems and suggestions that a closed-door systems role might never hear.
Offer a dependable way to ask for help and spend time observing a task where it happens. Ask what takes longer than expected and which workaround has become routine. Tommy also describes a colleague's idea for a MySpace-style internal record, still an idea he wanted to pursue at Summit 2025. Invite that kind of contribution, then test whether a proposed design helps people complete their work.
In the recording · 12:20 ↗Bring the useful design lesson home
Megan Story notices presenters doing more with their slides, delivery and perspective. She connects that creativity to staff training, portals, emails and dashboards, where the same care can make everyday work more engaging. The inspiration can travel beyond the conference room.
After seeing a strong example, identify the specific choice that made it effective. Was the next action obvious? Did the layout make a comparison easier? Did an example help someone understand the task? Try one change in a small view or training exercise and watch a colleague use it. Keep the improvement that helps them understand or act, rather than copying the whole presentation style.
In the recording · 16:54 ↗Leave the feedback loop open
Mike Dal Santo brings the conversation back to continuous improvement. Skills develop over time, and a completed build can still benefit from questions and feedback. He encourages seeking that feedback during development and continuing after the initial work is finished.
At the next review, bring three things: one task people can now complete, one exception that still needs help and one question to investigate. Choose a manageable adjustment and its owner. Keep the instructions current as the system changes. Across these seven conversations, a first spark becomes dependable shared work through repeated attention to the people learning, using and improving it.
In the recording · 23:13 ↗