About

This newsletter is called Adjust Accordingly because that’s the only honest advice anyone can give you about technology decisions. Here’s the evidence. Here’s what it means. What you do with it is your call.

One essay a month. Each one takes a real question about AI adoption, engineering decisions, or technology leadership, applies the best evidence I can find, and ends with something specific you can actually do. If I’m wrong - and I will be, occasionally - I’ll tell you next month.

I reserve the right to change my mind. That’s not a hedge. It’s the editorial policy. Evidence changes. Context changes. Anyone who tells you their position on AI adoption is final hasn’t been paying attention.

This newsletter is for engineers as much as leaders. If you’re making decisions about AI in software engineering or making the case for those decisions - it’s for you.

Some of what you’ll find:

• How to run a pilot that might actually fail, and what to do when it does

• Why ‘lines of code’ is the worst metric you can track

• The difference between a prompt and a skill and when each one wins

• What devs are actually thinking when you announce an AI initiative

• The investment case that almost didn’t get funded, and what changed

I’m Kelsey - software engineer/psychologist turned IT project manager. While I love software and problem solving I am, at heart, an eternal team optimist which is how I ended up in project management.

I’m writing a book called “The Demo That Worked Once”. This newsletter is where I think out loud while I write it, and where I’ll keep thinking out loud after it’s done.

Subscribe. Unsubscribe any time. Adjust Accordingly.