-
Open Bank is a faith-based community bank built on relationship banking. The brief was an institutional story deck — the kind of document that has to work in an investor meeting, a branch onboarding, and a partnership conversation without being rebuilt for each one.
The difficulty in a deck like this is never the visuals. It's that the source material arrives as four unrelated kinds of information: a chronology stretching back to 2005, a geographic footprint across the United States, growth figures, and a set of people and community commitments. Each one wants a different form. Presented as a uniform run of slides, they flatten into noise, and a reader who joined the room for one of the four leaves without it.
I structured the deck as four distinct movements — Our Journey, Our Network, Our People, Our Growth — and gave each one the form its information actually needed. The history became a horizontal timeline that reads as continuous momentum rather than a list of dates. The footprint became a California map where branch density is visible at a glance instead of requiring a table lookup. Growth and community work carried the same header system and green accent so the reader always knows where they are in the document, even joining mid-deck.
Newsletters
-
Translated raw institutional material [milestones, branch data, growth figures, foundation activity] into a structured narrative sequence
Built a slide component system (headers, accent rule, color, type scale) applied consistently across the full deck
Designed the data views: the chronological timeline, the domestic network map, and the growth section
Art-directed photography selection and treatment to carry the relationship-banking positioning
Extended the system to the Open Stewardship Foundation section so the community arm read as part of the same institution
-
Information architecture on a document instead of a screen. Deciding what a reader meets first, what can wait, and what has to be visual rather than verbal — then enforcing that decision across dozens of pages with a component system. That's the same work as structuring a multi-step flow, with the same failure mode if you get the order wrong.