Underlying Philosophy

Organizations should not rely on heroic staff to compensate for broken systems. In many nonprofits, critical work depends on institutional memory, informal processes, and individual workarounds. While that can sustain an organization temporarily, it becomes fragile under growth or stress. Sustainable organizations reduce unnecessary friction by building processes that are clear, repeatable, scalable, and adaptable.

Major Questions

• How does work actually get done?
• Where does work slow down, break down, or create unnecessary burden?
• Which processes create work without creating value?
• Where are approvals or communication creating bottlenecks?
• What depends too heavily on institutional knowledge?
• Where are staff creating workarounds to compensate for broken systems?
• Are responsibilities and workflows clearly understood across teams?

Seminal Documents

• Standard Operating Procedures (SOPs)
• Process Maps & Workflow Documentation
• Decision-Making Frameworks
• Cross-Functional Communication Protocols
• Meeting & Reporting Structures
• Operational Playbooks

What I Bring

I have spent much of my career building operational systems inside growing nonprofits where processes were informal, inconsistent, or heavily dependent on institutional knowledge. My work has included redesigning workflows, developing operational infrastructure, creating cross-functional processes, and stabilizing environments during leadership transitions and organizational strain. I approach operations as a practical discipline focused on reducing friction, clarifying accountability, and helping teams spend less time navigating systems and more time advancing the work itself. 

---

What – The Tools and Technology

Underlying Philosophy

Technology should support the work, not become additional work. Many nonprofits accumulate disconnected systems, duplicate reporting, and manual processes as they grow. The issue is usually not a lack of technology but the lack of alignment between tools, processes, and organizational needs. Good systems create visibility, trust, and operational efficiency. Poor systems create frustration, shadow spreadsheets, and unreliable data.

Major Questions

• Are systems supporting the work or fighting it?
• Is data accessible, accurate, and trustworthy?
• What work is being done manually that could be automated?
• Are systems integrated or fragmented?
• Do teams rely on shadow systems outside official platforms?
• Can leadership confidently use existing data for decision-making?
• Is technology reducing burden or increasing administrative overhead?

Seminal Documents

• Technology Roadmaps
• Systems Architecture Documentation
• Data Governance Policies
• CRM/Data Dictionaries
• Reporting & Dashboard Frameworks
• Automation Documentation
• User Adoption & Training Materials

What I Bring

I bring deep experience designing and managing technology systems that support operations, evaluation, and organizational decision-making. My work has included Salesforce administration and optimization, automation development, reporting infrastructure, dashboard creation, and integrating systems across departments with different operational needs. I focus not just on implementation, but on usability, adoption, and ensuring technology reduces administrative burden instead of adding to it.