Thinking about the tools I'm building and the programs I'm developing - that seems more akin to the way I want my job to evolve. As a "knowledge gardener."

So I've decided that my next 5 years will be spent as a "knowledge gardener." Helping people get the information they need. Encouraging people within my organization to talk to each other and share what they know. Facilitating learning when they need and want it (preferrably in much smaller chunks than they are getting now).

Scenario-based design of information technology addresses five technical challenges: scenarios evoke reflection in the content of design work, helping developers coordinate design action and reflection. Scenarios are at once concrete and flexible, helping developers manage the fluidity of design situations. Scenarios afford multiple views of an interaction, diverse kinds and amounts of detailing, helping developers manage the many consequences entailed by any given design move. Scenarios can also be abstracted and categorized, helping designers to recognize, capture and reuse generalizations and to address the challenge that technical knowledge often lags the needs of technical design. Finally, scenarios promote work-oriented communication among stakeholders, helping to make design activities more accessible to the great variety of expertise that can contribute to design, and addressing the challenge that external constraints designers and clients face often distract attention from the needs and concerns of the people who will use the technology.