Who?
Understanding the people.
Who is this for? Who is asking for this? Who experiences the problem most often? Who will use this daily? Who will be affected by the solution? Who are we overlooking?
Before we build,
I have a few questions.
Okay, probably more than a few.
Hello. I'm Micah, a Software Product Manager who approaches problems from more than one angle. I challenge assumptions, connect different perspectives, and help teams figure out what software is actually worth building.
Then I help make it happen.
I speak fluent stakeholder.
Different perspectives = Better product
I've worked across the teams that bring digital products to life. I understand their priorities, their constraints, and help get everyone working toward the same goal.
And yes, “it should be simple” means something different to every department.
How I think
The four big asks.
Where, when, and how didn’t make the cut.
The right questions help reveal the real problem, uncover different perspectives, and open the door to better solutions.
What?
Defining the problem.
What problem are we trying to solve? What isn't working with the current approach? What are people doing today to solve this? What assumptions are we making?
Why?
Challenging assumptions.
Why are we doing it this way? Why do we believe this is the right solution? Why isn't the current approach working? Why would someone change what they're doing today?
What if?
Exploring possibilities.
What if we looked at it differently? What if we’re solving the wrong problem? What if we made it simpler? What if everyone is right, just from different perspectives?
Sometimes the best solution starts with a question nobody expected.
Selected work
Questions asked. Problems solved.
I don't believe in jumping straight to solutions. Sometimes the best place to start is with a question.
Here are a few examples of where those questions have taken me.
01 / Newtek Business Services
Why did offering an existing customer another product take nearly an hour?
Explore the project →Two disconnected systems, too much information, and a lengthy pre-application process were getting in the way.
By talking with support, business, product, and development teams, I helped turn a complicated workflow into a streamlined dashboard with relevant recommendations and a simplified application.
The result
From ~60 minutesto Under 10 minutes
Explore the project →
02 / Talent Select AI
Can an asynchronous interview be both structured and human?
Explore the project →We had three months to build an interview product, and plenty of competing opinions about how it should work.
Through research, prototyping, and collaboration with stakeholders ranging from an I/O psychologist to executive leadership, I helped shape an experience that balanced assessment requirements, employer flexibility, and candidate needs.
The result
A completed, internally tested product that balanced structure with usability.
Explore the project →03 / On Q Financial
How do you build for 10× the content without 10× the bloat?
Explore the project →An ambitious SEO strategy needed a website that could grow dramatically, load faster than competitors, and still work with existing systems.
I collaborated with marketing and design to build a lean, custom WordPress experience with scalable content management, integrated SEO features, and preserved mortgage-agent search functionality.
The result
Faster than the competitors tested. A foundation still largely unchanged six years later.
Explore the project →About me
I didn't take the straightest path here.
And that turned out to be a good thing.
I've worked in marketing, designed interfaces, written code, solved business problems, and helped teams bring software products to life.
Each experience gave me a different way of looking at a problem—and a better understanding of the people responsible for solving it.
Today, I bring those perspectives together in Product Management.
I enjoy the part of a project where the answers aren't obvious yet. Where a good question can change the conversation. Where an idea starts becoming something useful.
I like figuring out what to build and working with others to build it.
I also know enough about building it to ask whether we're being realistic.
Curious by nature. Practical by experience.
Obligatory list of dates (PDF)
Don't just take my word for it
I'm bad at talking about myself. They aren't.
I've been fortunate to work with people who value my ability to connect business needs, technical realities, and the bigger picture.
Micah worked closely and collaboratively with engineers, helping connect product priorities with technical considerations. … Over the years, Micah became my most trusted colleague. There are very few people I have worked with whom I would want on my team as much as Micah.
He doesn’t “settle” but always seeks perfection in his work. With each new task Micah is able to either use existing knowledge to complete it, or obtain the knowledge through research and education, even if it means spending off hours obtaining that knowledge.
He has the ability to wear many hats and with that has taken on additional responsibilities that have been totally out of scope for what he was hired to do. He is one of those people that if you throw to the wolves he will come back with a pelt each and every time.
One last question
What are we building?
Whether you're developing a new software product, improving an existing one, or trying to figure out where to begin, I'd love to hear what you're working on.
I bring curiosity, cross-functional experience, and a practical understanding of what it takes to turn ideas into software.
Let's see what we can figure out together.