Team

Rich Nguon leads rhizae and is the accountable person on work the practice accepts, from scoping through handover. This node exists so that attribution in the graph points at someone rather than at a brand.

What the work draws on

Software development, applied data analysis, technical research, and systems design. The established capabilities on this site are the ones with delivery history behind them: software and product development, reporting and decision systems, and technical research. The research and evaluation capabilities are described as developing because that is what they are.

What one accountable person means in practice

The person who scoped a project is the person who hands it over. There is no account manager between the work and the client, and no team to absorb a commitment that turns out to be wrong. Where a project needs expertise the practice does not hold, a collaborator is named before work begins, as About the practice sets out.

What it rules out

Several large engagements at once, and specialist statistical or legal work outside demonstrated capability. Availability is a real constraint rather than a negotiating position, and it is the reason early projects are deliberately narrow.

How the work is organized

Scope is set around a decision rather than a deliverable, which is described in Approach. Attribution on individual projects distinguishes work done through rhizae from independent work and from prior roles.