Analyze
Requirements, process mapping, data investigation and testing. I write the solution design that developers build from, then test it end to end.
IT Business Analyst I · Minneapolis, MN
I turn unclear business problems into systems that work.
I am a Salesforce business analyst who also runs products, programs and AI automation. I take a fuzzy request, work out what is really needed, and stay with it until people are using it.
View this site as
- 4+
- years on Salesforce Service Cloud and Order Management
- 9
- AI agents co-built for delivery and program work
- 250+
- live conversations with those agents
- 150+ hrs
- estimated time saved, from my own conservative per-run estimates
What I do
Four kinds of work, each with proof below.
Own the product
Backlog, phase planning and stakeholder decisions. I have covered Product Owner duties through a launch and a leave.
Run the program
Intake, governance, vendors and reporting for a digital adoption program across several business applications. I own the board and the vendor relationship day to day.
Automate with AI
I design agents that take repeat work off a team. Anything that creates or changes data waits for a person to approve it.
Featured work
Projects I built or led. Work for an employer is described in general terms.
Live at work AI automation
AI agents for delivery and program work
I co-built 9 Atlassian Rovo agents with a teammate to take repeat work off a Salesforce delivery team. We built them side by side, and I use them in my day-to-day work.
- Story readiness reviewers flag missing detail and open questions before refinement.
- A story creator and a discovery intake agent draft work from ideas and wait for approval before creating anything.
- A documentation generator writes up completed work, and an issue investigator checks live records against what the team has written.
- Two program agents help manage a digital adoption board.
Read the case study: replacing a six-month spreadsheet with a ten-minute question
250+ live conversations so far, with an estimated 150+ hours saved. The hours are my own conservative per-run estimates, not a measured study.
Atlassian RovoAgent designPrompt designJiraConfluence
In development Side project
Stratus for Jira
A Jira app I designed that turns Salesforce release updates and security risks into tracked Jira work, so admins stop copying deadlines out of Salesforce by hand.
- It shows a preview of what it will create, then makes one ticket per issue with a due date and a plain-English note.
- It updates due dates when Salesforce changes, and it leaves alone any ticket a person edited or closed.
- It runs a daily check and never creates duplicates.
- The product brief, positioning, requirements and backlog are mine, and I built it with AI coding tools.
Running in a personal test setup. Not yet listed on the Atlassian Marketplace.
Atlassian ForgeJiraSalesforce APIJavaScriptProduct discovery
Live at work Program management
Digital adoption program
I set up how a large company manages requests for in-app guidance, from first idea to launch and measurement, and I run it day to day.
- I built the intake and prioritization process in Jira Product Discovery, with readiness criteria for new requests.
- I own the board, the priorities and the vendor relationship day to day.
- I run a weekly team meeting and monthly sessions with each business area.
- I moved requesters from one-off content asks toward business problems, and I planned a learning event for about 70 people.
WhatfixJira Product DiscoveryGovernanceVendor managementAdoption analytics
Supported Product ownership
Platform launch and next-phase plan
I joined a Salesforce order-management team during a critical transition, supported launch and stabilization, and covered Product Owner duties.
- I supported go-live, hypercare and production issues, and routed each problem to the right team across Salesforce, integrations and telephony.
- I ran backlog readiness, sprint planning and sprint reviews so delivery stayed steady during a Product Owner leave.
- I consolidated scope, estimates and dependencies from several teams into one plan for the next phase.
- I separated transformation work from run and improve work.
BacklogPhase planningHypercareStakeholder decisionsSalesforce
More work
Order approval workflow
I led analysis from requirements through testing, training, release and post-launch support, and presented options for handling historical orders.
Routing skills component
I specified a custom Salesforce component that lets supervisors change agent routing skills, from requirements through release.
File and image management
I delivered requirements, testing and enhancements for a custom Salesforce file and image solution used in service and community workflows.
Reporting accuracy investigation
I traced inaccurate turnaround-time reporting to its source data using SOQL and log analysis, then turned the findings into work the team could act on.
Help Center redesign research
I ran interviews and research, then presented recommendations on search, chatbot, accessibility, mobile and eCommerce integration.
Regression and end-to-end testing
I wrote test scenarios and ran end-to-end and user acceptance testing for releases, and documented a regression suite for the platform.
System documentation library
I wrote 500+ pages of process, data model and integration references, and checked them against the system before they were published.
Business Analyst Roundtable
I started a recurring practice group to improve user stories and acceptance criteria, with onboarding guides and Jira standards for new analysts.
AI adoption for the team
I help shape how a Digital Technology team approaches AI, including prompt playbooks for Jira, Confluence and requirements work.
Toolbox
The tools I work in every day, and how I use them. Pick a tool, then try the mock-up. All of them use made-up data.
Planning and intake
Jira and Jira Product Discovery
I use Jira as the front door for a whole program.
- One card per request holds the idea, requirements, testing and launch, so nobody has to hunt through chat for the latest update.
- Readiness criteria decide when a request can move to Ready for delivery.
- A rule fires when work moves to Done and hands it to an agent that writes the documentation.
- An intake agent interviews the requester and drafts the idea, then waits for approval.
JiraJira Product DiscoveryAutomation rulesDashboardsJQL
ReadyWalkthrough for the new case page
DeliveryReminder pop-up for order deadline
DoneReminder pop-up for order deadline
Documentation page created
Knowledge and agents
Confluence and Rovo
I treat documentation as the knowledge base that my agents and my teammates both read.
- 500+ pages of process, data model and integration references sit in numbered folders, and each was checked against the system before it was published.
- A documentation agent writes up each completed item and files it in the right folder.
- Story reviewer agents read that library to point out what is missing before refinement.
- Any agent that creates or changes something waits for a person to approve it.
ConfluenceAtlassian RovoAgent instructionsDocumentation structure
Is this story ready for refinement?
Mostly.
Clear: who it is for, two criteria.
Missing: what happens if the file is too large.
Open question: who approves exceptions?
I did not change the story. Want a suggested rewrite?
Suggested criterion:
When an export is larger than 10 MB, the user sees a message and can choose a smaller date range.
AI tools
Claude, Claude Code and Copilot
I treat AI like a capable new teammate. It gets written ground rules, and it has to show its evidence.
- Claude and Claude Code help me analyze Salesforce setup and data, check stories against a test environment and draft requirements.
- Copilot covers Microsoft 365 work, using prompt playbooks I wrote for the team.
- Every project gets a short instruction file that says what is read-only, what needs approval and what never to claim.
- I re-derive numbers before I repeat them, and I label estimates as estimates.
- I have worked with AI tools for about four years, and I use the same approach to help friends and family build agents of their own.
ClaudeClaude CodeMicrosoft CopilotPrompt playbooksEvaluation
Read-only unless I say otherwise
Looking is safe. Changing things needs a clear yes.
Show a draft before anything is posted
A draft costs a minute. A wrong post costs trust.
Re-derive every figure before repeating it
Numbers copied from old notes are where mistakes hide.
Label estimates as estimates
People should know what was measured and what was a good guess.
Ask before anything outward-facing
Messages and posts reach other people, so I approve them first.
Everyday work
Microsoft 365: OneNote, Outlook, Excel, Teams and PowerPoint
This is where most work actually gets communicated and remembered. I set these tools up so the busywork takes care of itself, because an inefficient process is not worth my time.
- OneNote: I keep notebooks for each type of project, plus handwritten weekly notes. A Copilot notebook for each team pulls in my notes and meeting recaps. It also connects to Loop, so I can ask what we decided last time.
- Outlook: rules and categories separate notifications from messages that need me, and scheduled Copilot tasks watch my inbox.
- Excel, Power BI and Tableau: I use them for data analysis, lookups across several sheets and charts. When the data sits in a database, I build the visuals in Power BI or Tableau.
- Teams: I share a link to the source document instead of pasting its contents, so everyone works from the current version.
- PowerPoint: my decks follow a repeatable shape, and I change the level of detail for business, technical and training audiences.
OneNoteLoopOutlookExcelPower BITableauTeamsPowerPoint
+Handwritten notes
My weekly notes and meeting notes are handwritten.
+Meeting recaps and transcripts
Teams recaps flow in, including meetings I facilitate.
+Loop pages
Shared Loop pages connect to the notebook too.
→One Copilot notebook per team
Each team I support has its own notebook, so answers come from the right context.
?What did we decide last time?
I ask in plain language and get an answer drawn from my notes and the meetings.
Try it yourself
Three small tools you can use right now. They run in your browser with made-up data, and nothing you enter is sent anywhere.
Business analysis
Story quality checker
Paste a user story and get a score out of 100, an INVEST check, what you did well and your top fixes.
INVESTAcceptance criteriaAgile
Product ownership
Backlog prioritization workbench
Adjust the sliders on eight made-up backlog issues, then switch between two scoring methods, WSJF and RICE, and watch the order change.
WSJFRICEMoSCoW
AI enablement
Agent guardrail designer
Choose what an AI agent is allowed to do, then see its risk level, the approvals it needs, and a simulated run that stops for a person.
Human in the loopRiskGround rules
Skills
What I use, and where it shows up in the work above. Search for a tool or a skill to see where it appears.
Business analysis
RequirementsUser storiesAcceptance criteriaProcess mappingSolution designRoot-cause analysis
Product and delivery
Product ownershipBacklog refinementSprint planningRelease readinessHypercareRoadmap planningRisk and dependencies
Program management
GovernanceIntake and prioritizationVendor managementStatus reportingChange enablementAdoption analytics
AI and automation
ClaudeClaude CodeAtlassian RovoMicrosoft CopilotGoogle GeminiAgent designPrompt designWorkflow automation
Salesforce and integrations
Service CloudOrder ManagementExperience CloudOmni-ChannelMuleSoftFive9Email-to-Case
Data and testing
SOQLSQLSplunkPower BITableauExcelUATRegression testingData validation
Tools
JiraJira Product DiscoveryConfluenceWhatfixSmartsheetMicrosoft 365
How I work
Turning ambiguity into a plan
I take a messy request and come back with scope, options and a recommendation.
Stakeholder alignment
I keep business, developers, QA and vendors working from the same decisions.
Clear writing
I write stories, plans and documentation other people can act on without a meeting.
Fact from assumption
I say what is confirmed and what still needs checking.
Ownership
I stay involved from discovery through launch and stabilization.
Efficiency
I keep changing how I do things. Doing the same thing and expecting a different result is not a plan, so I look for a better tool or a shorter path.
Teaching others
I run a practice group and write onboarding guides so the team gets better together.
Experience
Four years, one direction: from taking requirements to owning outcomes.
- Jun 2022Business Analyst AssociateTurnberry Solutions
- Mar 2024Senior AssociateTurnberry Solutions
- Jun 2024IT Business Analyst AssociateAndersen Corporation
- Sep 2026IT Business Analyst IAndersen Corporation
Sep 2026 to present Current
IT Business Analyst I
Andersen Corporation · Oak Park Heights, MN
Promoted in September 2026. Before that I took on acting Product Owner coverage, digital adoption program management and AI automation work alongside analyst duties.
Jun 2024 to Sep 2026
IT Business Analyst Associate
Andersen Corporation · Oak Park Heights, MN
Converted from contract to full-time. Led analysis for an order approval workflow, supported a platform launch, and started the Business Analyst Roundtable.
Jun 2022 to Jun 2024
Business Analyst Associate, then Senior Associate
Turnberry Solutions (Crew) · consultant assigned to Andersen Corporation
Ran discovery sessions and turned them into stories, acceptance criteria and prioritized backlogs for Salesforce Service Cloud work. Promoted to Senior Associate for greater ownership of requirements and stakeholder communication.
Credentials
Salesforce Certified Business AnalystCertification
Salesforce Certified AdministratorCertification
Professional Scrum Product Owner IScrum.org, 2026
B.S. EconomicsUniversity of Minnesota, Twin Cities, 2022
Beyond work
Things I build on my own time. They show how I work when nobody assigned the problem.
Ongoing Real-world AI
Building AI agents and skills with friends and family
The people I know keep asking me to help them use AI for real work, so I do. I have helped people in healthcare, finance, manufacturing and tech turn a daily annoyance into an agent or skill they actually use.
- Start with an interview, not a prompt. I ask about the problem, the process and how they want the result to sound before I write anything.
- Test before they rely on it. I write test scenarios, run them, score the results and revise the instructions.
- Work in the tools they already have. Their company's tools and permissions set the limits, so I build inside them.
- Teach them to adjust it. The goal is that they can change the agent themselves next month.
Complete Home tech
Smart TV cleanup
I removed ads, tracking and demo apps from a Google TV and a Fire TV, then replaced their home screens with a clean launcher.
- I switched off apps instead of deleting them, and kept an undo record so every change can be reversed.
- I backed up each device first and tested after every batch, one device at a time.
- I kept what the household uses: streaming apps, casting and the voice remote.
- I wrote a how-to so the same steps work on the next device.
Ongoing Data and automation
Fantasy football analysis tools
A weekly workflow that pulls league data, rates trade offers and checks injuries and weather before lineups are set.
- Small Python tools handle the repeat analysis, so each session starts from fresh data.
- Any message to another team owner waits for my approval first.
Off the clock
Usually on a lake or a golf course.
I fish for walleye, bass, pike and muskie, hunt in the fall, and play golf around Minnesota. I would rather be outside than almost anywhere else.
It shapes how I work too. I like to prepare well, read the conditions, stay patient and learn something from every trip. People are more than their job titles, so here is a bit of mine.
WalleyeBassPikeMuskieHuntingGolf
Press the ball to send it down the fairway again.
Let's talk
I like talking about product ownership, program management, AI enablement and Salesforce work. The best way to reach me is LinkedIn.