Distinct roles, shared work
Robby Prochnow owns and leads Zen Aegis. He also serves as CTO of Common Ground Ventures and its Technology and AI Architecture principal. Those roles connect his technical practice with the group’s broader work.
The technical role spans the connection between a business question and a system people can use. It involves understanding the process, selecting a useful scope and carrying design decisions into implementation. Within the collaboration, that work can be discussed alongside the commercial, operational and creative questions that affect whether a system will be useful.
Work through the people doing it
The collaboration brings technology into conversations with other disciplines. Robby contributes the work of designing and building systems; the group provides a setting for practitioners to work together.
Kinwork is a Zen Aegis platform in rollout.
For Zen Aegis, the useful part of working across disciplines is the ability to bring a concrete workflow into a broader conversation. A technical implementation still needs a purpose, a person responsible for it and a way for its users to understand it. Those concerns belong together when deciding what to build.
About this build
Jesse supplied the original wiki material and the publishing approach. This edition adapts the ZA material into the existing Zen Aegis website, with a reusable layout and a separate source record for each page.
The public accounts use the Zen Aegis perspective, describe clients by type and distinguish delivered work from developing applications and demonstrations. Credits follow the work: Robby leads the Zen Aegis practice, and Jesse contributed the original wiki material and publishing approach.
The pages are organized around the work rather than a list of tools. A reader can move from the practice overview into a delivered engagement, an operating approach, public code or a prototype and see the relevant distinction. That structure gives future updates a place without blurring one kind of evidence into another.
Keep the record useful
The point of this wiki is a readable account of the work that can be maintained as it changes. A project’s status and evidence should change with it, without turning a possibility into a result.
Zen Aegis maintains this record as the work changes. Each page carries its own status and, where appropriate, public background sources, so readers can distinguish an account of delivered work from an exploration of what comes next.
Questions & answers
A few useful distinctions
Who owns and leads Zen Aegis?
Robby Prochnow owns and leads Zen Aegis.
What is Robby’s role at Common Ground Ventures?
He serves as CTO and Technology and AI Architecture principal.
How does the collaboration relate to Zen Aegis’s work?
It connects Robby’s system design and implementation work with practitioners from other disciplines. The focus is the work they can do together.
What is Kinwork’s status?
Kinwork is a Zen Aegis platform in rollout.
Who contributed the original wiki material?
Jesse supplied the original ZA wiki material and the publishing approach. This edition adapts it into the existing Zen Aegis website.
Why are clients described by type?
The cases explain the workflow and its status while preserving client and prospect anonymity. The organization’s identity is not needed to understand the work.
Public sources
These links provide the public material and background identified below. Client engagements are described by type.
- Zen Aegis — about the firm
Public background on the Zen Aegis practice.
- Common Ground Ventures
The collaborating group’s public website.