Barbara Christine


2011 –

The story of each project is unique. — Christos

Ask any consultant what they like most about their job and you will get a one word answer: Projects. Lots of them. All kinds of them. In all kinds of industries. With all sorts of deliverables. No two are the same.

Public sector sites to retail sites... Small local companies to large global corporations... Tools to operate a game studio, tools to help with tax forms, tools to manage the supply chain... And intranets from just about every industry. Whomever said, "Variety is the spice of life" must have been a consultant.*

* William Cowper (not a consultant)

“You can achieve more effective results when solutions are created, understood, and accepted by the people impacted.” — Michael Wilkinson

Facilitation is the thread that runs throughout all these projects. As a certified facilitator, I have conducted meetings and workshops for design sprints, customer journeys, persona development, requirements gathering, retrospectives and more.

In addition, I also conduct training to teach facilitation principles to colleagues and clients.

“Learning is not compulsory... neither is survival.” — W. Edwards Deming

Industry Knowledge Content Analysis | Enterprise Tool Design | Experience Design | Information Architecture | Mobile Applications | Prototyping | Storyboarding | Training Classes | Usability Testing | User Research | Visual Design | Workshop Facilitation

Methodologies Agile | Design Sprints | Design Systems | Rapid Prototyping | Requirements Visualization

Tools & Technologies Abstract | Axure | Bootstrap | CSS | HTML5 | InVision | Photoshop | Illustrator | Sketch


“If you can't describe what you are doing as a process, you don't know what you are doing” — W. Edwards Deming

Yes, every project is unique (see The Projects). And while that may be true, the process for each project generally follows the same pattern:

  • Start with some research — into competing products...or for design inspiration... or how other industries approach a particular process.
  • Then, using a Requirements Visualization method tailored for each project, facilitate meetings with actual users (or their surrogates) to ferret out the requirements they want to see as part of the site or application. We generate tons of ideas, we sketch, we whiteboard, we live on post-it notes - all as a means to quickly come to consensus on goals and features (aka Design Thinking).
  • Next up is prototyping - Low fidelity to highly interactive depending on the project. This step brings the design to life and is perfect for...
  • User testing. Because YOU are not the user and there is no better way to validate a design.
  • Finally, incorporate user feedback into the design and continue iterating until an agreed upon candidate is handed off to developers.

Not only is this an efficient method to quickly gain consensus on the design, it's also cost effective as no code is written until the design churn has died down.

Customer Journey Maps • Information Architecture (I/A) Diagrams • Personas • Process Improvement Maps • Prototypes (HiFi - LoFi - Interactive) • Redlines • Screeners and Test Plans • Sketches • Style Guides / Pattern Libraries • Usability Testing • User Research Readouts • User Workflows • Wireframes • Workshops