Audience + Lifecycle.

Audience [structure: for – who have – in an – that – unlike – the product]

For people who consider themselves "non-technical" or assume that learning code is something they would never do, yet who have – at least abstractly – a preference for greater control over and knowledge of the digital products and services they interact with. Additionally, anyone who feels anxiety about technology with a likely root being in their "limited" understanding.

My intervention will ideally live in an everyday or casual learning context that will generate understanding, insight and mental tools for thinking about technology and beyond. Some aspects may lean towards making leaps from creative concepts to execution, in this case the emphasis is on a creative development context.

Unlike simply using technology, or even customizing it, the intervention should empower people in both creative ability and critical thinking around technology. I imagine a different socio-cultural impact to the 'learn to code' movement (which, while constituing many fantastic initiatives, focuses acutely on the tools – perhaps like learning vocabulary and grammar rather than a higher level consideration of literature, to draw a somewhat unfair analogy).

The product should support enhanced "procedural literacy" and insight into technology, with a higher order goal of closing the gaps and psychological leaps between the three component steps of software development:

concept < > logic < > symbolic notation

Lifecycle

Discover / Explore / Learn / Reflect / Extend

For Exclusion

My ideas aren't quite narrow enough yet to clearly indicate this, but broadly: not developing a new programming language or any such radical solution, nor a fully-featured new development tool. I'm seeking a limited scope to encapsulate some of these much larger ideas in the hope that through explanation and demonstration the audience can extrapolate.