Rigorous Syntax

Reggie, CTO

Systemkey™ from STETA can help you “Embed Experience in Printsm” because the rigorous syntax of the model allows you to eat the elephant a bite at a time (or in tech-talk, to perform your analysis in layers) and pick up directly where you left off your last session. Systemkey™ is one of the few architectures under which an integrated risk analysis is even possible (as opposed to siloed reports stapled together with a cover sheet) and just as importantly, one in which doing a partial analysis is free of roll-up errors because of the consistent data set's summary codes.

I Need Systemkey™

^top

Domain-flexible Grammar

Albert, CFO

You already know (or the market's ruthless march to globalization will teach you) that truly integrated risk analysis is a must, accounting for both the forest AND the trees. At the requirements level of abstraction Systemkey™ is the three way match between fast versus cheap versus right. Systems Thinking tells us how to scale our view to the right level of detail. Systems Engineering tells us what to do with the data we find. The model's flexible grammar means that we're not wasting time or money remapping our processes to match hard-coded choices someone decided for us.

I Need Systemkey™

^top

Systemkey™ scales: As you do more work, it takes the same or less effort

Dave, CEO

Power of the model comes from restoring the rich cream of local context to the skim milk of traditional analysis.

• Mintzberg, H., “An Emerging Strategy of ‘Direct’ Research” Admin Sci Qtrly, Dec 79, 24(4): 582-589.
• “As soon as the researcher insists on forcing the organization into abstract categories—into his terms instead of its own—he is reduced to using perceptual measures, which often distort the reality. The researcher...can only ask people what they believe, on seven-point scales or the like. He gets answers, alright, ready for the computer; what he does not get is any idea of what he has measured.…The result is sterile description, of organizations as categories of abstract variables instead of flesh-and-blood processes.” (pp. 585-586)



Ernest, CIO

The Systemkey™ folks get it. They follow James Gosling's advice on how to scale: …the way you do scaling is you step back from any particular implementation, abstract from what the service is, and then as you run up and down the scaling chart, you switch from one implementation to another.


I Need Systemkey™

^top

Content Section 3 Header

Section 3 intro

Staff Name

• Topic 3-1 Header, Text 3-1
• Topic 3-2 Header, Text 3-2

I Need Systemkey™

^top