Sean Conner

I typically create content models by starting with broad brush strokes, which is all well and good when thinking about content marketing goals, music apps, or event sites, but gets a bit meta when answering the question, Just who is Sean?

For this site, I roughed out the following, some of which made it into the site after a dedicated design sprint.

Conceptually, Sean …

Has “Thoughts” on various things, that can be posted online for others to read (or ignore). These are written by an "Author" named Sean (but maybe a Sean wearing a certain hat, see "roles" below)
Organizes thoughts in “Notebooks,” a curated collection of Thoughts on certain topics or ideas–Content, Doodling, Leadership etc.
Collects “Bookmarks”: ideas and insights from others, whether books I’ve read, articles that inspire, quotes, etc. (This didn't make it into the site)
Has “Roles”
- Content Engineer vs Product Manager vs People Leader vs Kansan vs Board Game Designer vs Sometimes Doodler
- Which might be tied to "Jobs" that define a "Career"
Sometimes “Doodles”
Plays “Board Games”

For the site MVP, I focused on "Thoughts" as a type of article or blog post; implemented the Roles idea as "Author," with just a single Sean for now; and stood up rough structures for categorization and notebooks. The rest has been shoveled into a later pile.

(I'd be remiss not giving some shout-outs to a few folks who've informed my approach to content modelling, from Karen McGrane and Jeff Eaton at Autogram, to Cleve Gibbon's Content Modeling Series, to Carrie Hane and Mike Atherton who wrote Designing Connected Content.)