How I engineer
Environmental Design
Over a decade in sustainable and secure system design for the built world, from infrastructure to connected environments.
Authored Agile Methods
Author of “SISE: Snap‑In Systems Engineering,” a practical method that brings systems engineering to lean organizations without heavyweight processes.
Engineer by Hobby
Nearly three decades building hardware, software, and systems of systems – not only as a profession but as a long‑running hobby.
System design for everyone with SISE
Systems engineering enables projects to be executed on‑time, on‑budget, and within scope – but traditional processes often overwhelm lean organizations. Many teams use pieces of systems engineering informally and inconsistently, which limits the benefit and adds confusion.
The Snap‑In Systems Engineering (SISE) method follows the classic systems engineering “Vee” model while emphasizing an agile, modular approach that is easier to adopt and scale. Each “snap‑in” option minimizes the amount of systems engineering knowledge required, while still emphasizing measurable, project‑level results.
SISE is designed for teams that need rigor but lack the time, budget, or staffing to implement full‑blown frameworks. It provides flexible patterns that let you select the right level of process based on project complexity and criticality.
Get the SISE book on Amazon- Adapting the “Vee” model for lean teams
- Snap‑in options for different project types
- Case study of SISE in a real‑world project
- Emphasis on time savings, cost control, and positive outcomes
“SISE is systems engineering for the rest of us.”
Why SISE matters
In many organizations, academic methods are hard to implement and traditional frameworks are too heavy for the realities of tight timelines and small teams. SISE bridges that gap by providing just enough structure to reduce rework and risk while preserving agility.
The method is designed to help teams reduce late‑stage surprises, improve alignment between stakeholders, and create a clear line of sight between requirements, architecture, and verification.