Peter Odum

Captricity takes in hand-filled paper forms, processes them, and returns collated and formatted computer data or whole databases from them.

To do this, Captricity uses sophisticated character recognition A.I., supplemented by Mechanical Turk-style human review. This process returns uncannily (99.3% or better) accurate data. 

I produced this graphic for internal staff and external use with specific clients, to show the basics of the process. 

Captricity's system has clients (insurance companies, government agencies, etc.) define regions on paper forms, where each region defines a piece of data.

I used prior game design experiences with tips and tutorials to revamp this system, making it easier to use without lengthy instructions. I added simple graphical tips, refined visuals, a focus state for the selected field, and other controls for defining areas, streamlining this process to be easier to follow and not error-prone.

Not only did staff and users love these changes - they reduced customer service calls and costs significantly. 

I wrote design requirements when necessary as this kind of document helps keep not just UX staff but the entire production team on the same plan.

At Captricity these were often the first documents tracking fundamental project requirements, user stories, and basic definitions of key terms. 

User Flows can be minimal, indicating screens/functionality simply as boxes.

These were used to understand essential processes and interactions, and could be used before screen wireframes yet existed.

Whenever possible I sketch on whiteboards or paper before moving (if needed) to digital wireframes and prototypes. Sometimes I do several rounds of wireframing this way, as it allows for quick iteration and collaborative discussion.

Here I used a composite of several whiteboard images to document initial decisions. This evolved into a digital document with more precise wireframes replacing the sketched images.

Wireframes at Captricity are generally built into user flows, so one document supports multiple purposes, and staff do not need to track many different sources when implementing designs.

Key User Flows were identified by the team. Once they had been sketched, discussed and agreed upon, they were digitized in detail. 

User Flow documents are scaled such that they can be read as an overview, but the individual wireframes are also fully detailed, so flows and wireframes co-exist in one document. 

To guide implementation, I created tools to help developers build features with design in mind, and to triage for broad design issues before launching.

This pre-flight checklist suggested basic design aspects to watch for and simple references to key styleguide information.

This was delivered alongside a presentation reviewing checklist items and in particular the rationale behind some of the less-obvious design decisions. 

I built Captricity's Design Pattern Library to keep front end page code consistent, and to support creating broad visual and functional standards.