This shows a template that was part of a persona cookbook. Training teams that did not have UX resources on light research methods allowed improved communication and self direction on improving user experiences. I provided follow up reviews to assure quality.

I oversaw the creation of this tool kit including synching overall QA across Multiple teams. The kit was developed for a team of 14 product managers and around 50 developers who all were part of a 304 year effort on a large release. The purpose of this kit was to promote quick and efficient concept development , specification storyboards and prototypes. The kit was used from concept creation through user testing.2

Kit Detail: This shows the ribbons used in the application. Each ribbon represents multiple architects and development teams. The app was extensive, covering enterprise application development through business processes. Application creation could start in any SDLC phase  using this app.

The prototype kit was comprised of modular parts that shared behavior patterns while covering a wide range of experiences. UI that appeared where the user was focusing kept them on task and increased the intuitive nature of the UI. Consistent UI behavior patterns allowed cross persona users easy learning curves where they could concentrate on content rather than how the UI behaved.

This view shows workspaces, workpads within workspaces, and action panel behaviors. The example uses on of the business process design shapes from the business process ribbon.

A business process under construction, showing the contextual view as it would appear in implementation.

Testing design templates provides efficient template reuse with built in ease of use validation for future designs. Rapid Iterative Testing (RITE)  of application verifies customer acceptance criteria

Here is a more in depth process view integrating design and agile. This was produced to improve company understanding going into a product cycle.

This is a communication strategy that sets expectations for each stage from vision to agile design and implementation.

Showing an analysis of scenario breakdown from journey to discreet steps used in a user story for test. This method was adopted by the company as a way to be more agile from design to QA.

Here is a detail of the end to end user scenario. This provides consistency in direction for user needs, navigation, information architecture, early wire-framing, test planning, and design/development sprint planning.

This detail shows a process I developed, pitched, and gained buy-in from development and executive leadership. Using scenario steps and working with development to create use cases that can be tested pre-code. This increased efficiency in the company by reducing QA bottlenecks, code was no longer required to created test cases.

Create a unified experience across 12 teams all dedicated to Microsoft marketing. Scenario driven use created a common communication platform that drove cohesive site design for these teams