Adam's README
Contents
TL;DR
- Show me the mechanism. How it works, not what it’s called.
- Have an opinion. Vague, hedged answers give me nothing to push on.
- Write it down. A doc, repo, or diagram beats a slide deck.
- Argue with me. I’ll take either side to find the best answer. Lots of questions means I’m interested, not that I’m against it.
- I need ideas to land. I’m happy in an optional seat if my input moves the work. I check out when it doesn’t.
Who I am
I’m a consultant at Method, currently helping large companies in regulated industries understand how to position themselves for AI adoption. I started as an electrical engineer, then built mobile apps, then worked on developer platforms and software delivery, recently in finance.
Lately I’m working on ways of working with AI systems: if you capture what your organization knows (the stuff that lives in people’s heads) and build it into how your agents are set up, you get an advantage that lasts. I’m interested in the human factors that make AI adoptions successful. If you’re using agents in real work, tell me what’s working (or not). I also like talking about system design, agent protocols, developer platforms, and how organizations work (Deming, Scott, Toyota Kata).
Default settings
- Curiosity
- High
- I want to know why things happen. I dig until I find the real cause, look for the pattern, and usually fix it.
- Independence
- High
- Give me a goal, the limits, and room to work. I’ll trust you the same way.
- Tolerance for difficulty
- Oddly high
- A hard problem or an unreasonable trail run sounds like fun.
- Tolerance for pointless friction
- Low
- Red tape, unclear ownership, and process for show wear me down faster than hard work.
How I work
- Mechanism first. “It improves alignment” means nothing to me until you show how it works. Tell me the goal, the limits, and what’s been tried, with real examples.
- Source control is the source of truth. Work should live in a repo as code, config, or “specs”, and approvals should happen there.
- Kill toil, don’t codify it. I try to remove busywork with well-designed systems and tools. Putting a review step into a workflow tool doesn’t remove it.
- Watch the handoffs. Problems pile up between systems and teams, where nobody owns them.
- Share rough work early. I’d rather improve a working draft than polish a big reveal.
- Match care to stakes. If we can undo it, try it and learn. If we can’t, know the downside and how we’d spot trouble.
I argue to think
Arguing is how I test a tech choice, plan, or team direction. I’ll argue either side to see which holds up. I do this more than most people I work with, so:
- If I argue a position, I may not hold it. Ask whether it’s mine or devil’s advocate.
- Arguing back is the most useful thing you can do, live or in writing later.
- I’ll push back on a polished plan that misses the real problem. That’s about the plan, not you.
- Tell me if I’m steamrolling.
Communicating with me
- Skip the slides. Do the thinking in writing. A deck is fine afterward to present it.
- Feedback: give it to me straight, more direct than you’re probably comfortable with. If I’m wrong, show me why and I’ll change my mind. I’m happy to adapt to your style, so it doesn’t have to be mutual. I’m not scary.
- Tell me what you need from me: a decision, a review, someone to think out loud with, or help doing the work.
- Write first. Send a message with context, and ask for a call if we need to talk it through. I’ll push back on meetings that could be a doc.
- If something isn’t working, tell me plainly what happened and what you’d like changed. If I ask questions, I’m trying to understand, not defend myself.
What keeps me engaged
I do my best work when I’m learning something, on hard design problems, with a small, smart, curious team that has time to build things well (I love good UX). I don’t need (or want) the spotlight, and I don’t need to be the one writing the code. I lose interest in box-ticking, reports nobody reads, hype over quality, and having to play politics to be heard.
If you’re junior: I like mentoring. Show me rough work and expect specific feedback.
Logistics
- Remote, from the mountains west of Denver. Mountain time.
- Kid logistics make mornings hard. Check before booking.
- Sometimes mountain weather hurts my internet; if I drop, I’ll come back.
Known quirks
- I fix first, explain later. If you need me to share an idea sooner, say so.
- I overthink. Digging for causes can turn into too much thinking about principles. Tell me when it’s good enough.
- I take things on myself. If you want in, or I should hand it off, say so.
- I don’t check in much. Ask for more and you’ll get it.
- My standards can sound like criticism. I pick at details because I care about the result. Call me on it if you want me to stop or provide different feedback.
Outside work
Good ways to get me talking:
- Mountain running and ultras. Covering distance in the Colorado mountains to see the things that are out there.
- Climbing and backcountry skiing. Working back toward 5.12 sport; avalanche-trained (AIARE 1).
- Building and fixing things. Carpentry, plumbing, electrical, appliances, cars. If it’s broken, I probably want to take it apart. Also if it’s not broken (yet). Right now: making my house more fire-resistant.
- Mushroom foraging in the high country, and gardening and cooking with what I grow and find.
- Books. Mostly audiobooks on runs. Books I think are important: Infinite Jest, Bullshit Jobs, plus recent favorites: The Blade Itself, The Name of the Wind.
- Factorio. Not many other video games, but I like Factorio.
- Family. Married, two daughters, an old Belgian Shepherd mix, two cats, a few dozen chickens.




