Some things you won’t find on my resume.


I spent about 2 years trading cryptocurrencies and in that time, became really interested in the continuous token issuance model.

Why? Among other things, it could provide critical financial infrastructure for globally coordinated ventures.

Around the same time, I was also working on designing an online marketplace, which provided me with some context to experiment with several “how might we” type questions on the side.

Some of these ideas are actually being spearheaded by the team over at Relevant. It’s a community curated news platform that does 2 things differently. “likes” and “comments” inform (1) a contributor’s reputation and (2) the value of contributed content per a speculation market.

Websites in 1996

I taught myself coding and design skills in 1996 and earned my first $300 for a design when I was 14 years old. I ended up working as a brick mason after high school, however, and only returned to coding in 2012 when I relearned the modern application of web languages, began working with Node, and started working with a startup called Wava Media in Chicago.


During 2017 I began using technical analysis to inform trades on stock exchanges while studying under Nicola Duke. I loved this insightful, thought provoking, and highly addictive experience but eventually, put the brokerage accounts and my nerves to rest.


I inherited and fostered about 350-400 orchids for a year or so before donating them to the Illinois Orchid Society.


Lived on a boat in Key West and sailed the British Virgin Islands for 3 months while reading Wilhelm Reich’s work on character analysis, Bions, and Orgone.

I’m also a licensed Brick Mason

Before returning to the tech world, I often worked in construction. Specifically with bricks. I did for most of my time while studying Sociology and Political Science at Northeastern University.

The building on the left there, with the arches, that’s The Radler. To the right, you can see Emporium.

This set of projects, extending from the Fullerton and Milwaukee corner all the way to Slippery Slope, was one of my last working full-time in construction.

I’ve Worked With

High-level approach

This changes depending on the structure of the organization, the project’s challenges, and the team’s skillsets.

Defining the problem

Here we learn about the problem and opportunity space, the goals, the company’s plans, the project timelines and constraints.

Conduct the research

Learn about the market; the target user; competitor platforms or services; user reviews; mid-term market trends; review available analytics, heat maps, and so on.

Analyze the findings

While performing research, I’m also recording concrete data, observations, sketches, and design patterns that may be useful moving forward. These notes are discussed with stakeholders or internal teams to help carve out a path forward.

Define the parts

Depending on the project, product, and team we may create a story board; user stories; epics; diagrams; content maps; site maps; spreadsheets; content audits; and so on to begin concretely defining the shape and parts of the product on which we’ll iterate and sprint.

Layouts & Flows

We take the documents above, our macro vision, and begin realizing concrete layouts from our research in the form of rough wireframes and mood boards.

Visual Design & Development

Layouts are designed with additional reference to user findings and annotations. I generally work between visual designers, developers, and stakeholders to make sure our designs meet all usability, brand, and functional expectations.

Let’s Talk


Skype me


Call me

1 312 479 7825

My location

Chicago, Illinois