Diagnose the work
Find the recurring work where AI can help without erasing the human contribution or hiding the risk.
P/P About Premise & Practice
AI work design for people and teams.
AI gave more people the ability to build. Most organizations still run on workflows, queues, and handoffs created around a different set of limits. I built Premise & Practice to help people question those assumptions and prove a better path in real work.
Being technical now includes identifying the right problem, defining the work clearly, setting human boundaries, and verifying whether the result holds up.
Premise & Practice exists to make that judgment practical. Now You're Technical is the publication and learning community that helps more people build it.
The work moves through the same three disciplines whether the starting point is an Audit, a Build Day, an advisory engagement, or a personal career question.
Find the recurring work where AI can help without erasing the human contribution or hiding the risk.
Define the outcome, inputs, quality bar, exceptions, and approval points before choosing the tool.
Test the result against representative examples, use it in real work, and improve what fails.
Close enough to the work to know where the tidy story breaks.
Rusty leads Data, Innovation & Intelligence at a global industrial technology leader, where he helps nontechnical people use AI in consequential work.
He works at the intersection of AI, work design, data, and adoption. His focus is turning clear thinking into systems people can test and use responsibly.
He created Now You're Technical because access to AI became common while the judgment to choose, verify, and adopt the right work remained scarce.
Intel explains what is changing. Career X-Ray shows what changes for you. The Audit finds the work worth changing. Build Days turns one opportunity into a tested system. Executive Advisory helps leaders decide what earns the right to scale.
The work is practical, evidence-led, and designed for people who understand their domain even if they do not think of themselves as technical.
I will help you work out whether it belongs in an Audit, a Build Day, an advisory engagement, or somewhere else entirely.
Start a conversation ↗