Four tools for finding out what is actually going on before you design anything: a client intake framework, a tech stack decision framework, a CRM fit checklist, and a map-your-system worksheet.
Four steps to run before you touch a website, a workflow, or a program design: cover the current pain points, walk the customer's actual process, understand the business and culture, then build. Maps to Ecosystem Mapping and Workflow Design.
How to evaluate a tool before you buy it: assess the real need first, score options against your must-haves, and plan the integration before you commit. Includes the manual-first rule. Maps to Constraint Identification.
What you actually need to track, and the four signs you're about to buy the wrong tool. Maps to Dependency Analysis and Sustainable Operations.
A fillable table that surfaces your real bottleneck in about ten minutes: tool, content, frequency, audience, payment, and follow-up, mapped side by side. Maps to Workflow Design and Implementation Pathways.
These aren't theoretical frameworks. They're the tools I built and used running client engagements for years before I ever called it a "method," refined through digital literacy program design, workforce development, and policy facilitation work. They hold up in a small business as well as a civic program because the underlying problem is the same one every time: people design solutions before they understand the system they're designing for.
This toolkit is the starting layer of the full Sources Architecture Method™.
Start a Conversation