Senior Risk Analyst Jobs in Brodhead, WI (NOW HIRING)

Job Title:Sr. Business Analyst
Hourly/Salary Compensation Range:$60-$70/hour
Contract Length:Up to 3 years
Location:Remote (Central Time Preferred)
Hours:40/week
Start Date:End of August, 2026
Client Overview:The Wisconsin DHS Office of Health Informatics is a long-time partner of Medasource, having engaged over 200 consultants since 2020. They are currently undergoing and cluster of new projects, installs, and modernizations.
Job Description:
SENIOR BUSINESS ANALYST, PRODUCT MANAGEMENT AND SOFTWARE DELIVERY POSITION SUMMARY
Under the general direction of Project Delivery Unit Supervisor, this role provides senior business analysis and product management services for complex software implementation, modernization, and digital transformation initiatives.
The contractor serves as the primary liaison among program, business, product, operational, technical, data, vendor, and executive stakeholders. Responsibilities include analyzing business needs and workflows; eliciting, documenting, validating, and managing requirements; supporting product vision and roadmap development; prioritizing product backlogs; defining acceptance criteria; and ensuring that solutions meet user, business, technical, and regulatory needs.
The contractor leads or supports activities throughout the product and software delivery lifecycle. These activities include discovery, process analysis, solution evaluation, development, testing, implementation readiness, rollout, adoption, stabilization, and transition to ongoing operations.
This position requires extensive knowledge of business analysis, product management, requirements management, process improvement, software delivery, stakeholder engagement, and organizational change. Experience supporting technological solutions in public health, healthcare, government, or another regulated environment is strongly preferred.
GOALS AND WORKER ACTIVITIES
35% A. Lead business analysis, requirements development, and process improvement for complex software initiatives.
A1. Plan and lead business analysis activities throughout the software and product delivery lifecycle.
A2. Work with business owners, program leaders, users, subject matter experts, technical teams, and external partners to identify organizational needs, operational challenges, and desired outcomes.
A3. Conduct stakeholder interviews, requirements workshops, document reviews, observations, surveys, and other discovery activities.
A4. Analyze existing business processes, workflows, systems, data exchanges, roles, policies, and operational constraints.
A5. Develop current and future process maps, workflow diagrams, business rules, decision models, use cases, and supporting documentation.
A6. Identify process gaps, duplication, inefficiencies, risks, control weaknesses, and opportunities for standardization or automation.
A7. Elicit, analyze, document, validate, and maintain business, functional, nonfunctional, data, reporting, interface, security, privacy, and accessibility requirements.
A8. Break down complex business needs into clear, complete, testable, and traceable requirements.
A9. Facilitate agreement on requirements, business rules, scope boundaries, priorities, assumptions, and expected outcomes.
A10. Evaluate proposed requirements for clarity, completeness, feasibility, value, risk, and alignment with business objectives.
A11. Maintain traceability from the identified business need through design, development, testing, acceptance, and implementation.
A12. Evaluate proposed solution designs and system functionality against approved requirements and business processes.
A13. Identify conflicts, gaps, dependencies, and changes in requirements and facilitate their resolution.
A14. Recommend improvements to business processes, policies, workflows, data, or systems based on analysis and stakeholder input.
25% B. Provide product management and product owner support for software products and digital services.
B1. Assist business and program leaders in establishing the product vision, objectives, users, value, and measures of success.
B2. Translate strategic objectives, user needs, public health or program outcomes, and operational requirements into a product roadmap.
B3. Develop and maintain epics, features, user stories, use cases, business rules, acceptance criteria, and supporting product documentation.
B4. Establish and maintain a prioritized product backlog in collaboration with product owners, program leaders, technical teams, and users.
B5. Facilitate backlog refinement, release planning, sprint planning, product demonstrations, and product review sessions.
B6. Evaluate and balance user value, program outcomes, technical feasibility, cost, delivery risk, compliance requirements, and organizational priorities.
B7. Assist product owners and sponsors in defining the minimum viable product, release content, future enhancements, and deferred functionality.
B8. Support timely decisions concerning product scope, features, priorities, dependencies, and tradeoffs.
B9. Define measures for product performance, adoption, use, user experience, service quality, and outcomes.
B10. Gather and analyze user feedback, operational data, support trends, and performance results to recommend product improvements.
B11. Support product lifecycle planning, including implementation, enhancement, maintenance, operational ownership, and retirement of legacy systems or processes.
B12. Represent business and user needs during solution design, development, configuration, and implementation.
20% C. Lead or support solution validation, testing, implementation readiness, rollout, and evaluation following implementation.
C1. Develop test strategies, user acceptance testing plans, test scenarios, test cases, expected results, and acceptance criteria.
C2. Ensure that test scenarios provide appropriate coverage of requirements, workflows, business rules, data, interfaces, reports, user roles, and exception conditions.
C3. Coordinate user acceptance testing with business owners, end users, technical teams, vendors, and other stakeholders.
C4. Monitor testing progress and ensure that defects, requirement gaps, and design issues are documented, prioritized, and resolved.
C5. Validate that completed functionality satisfies approved business requirements and acceptance criteria.
C6. Support data conversion and migration by defining business rules, validation criteria, reconciliation requirements, and processes for handling exceptions.
C7. Evaluate business and operational readiness for a pilot, phased, regional, program level, or organization wide implementation.
C8. Assist in developing plans for implementation, cutover, contingencies, rollback, focused launch support, and transition to operations.
C9. Develop or review job aids, standard operating procedures, workflow documentation, training materials, and user communications.
C10. Support launch activities and provide business analysis assistance during stabilization and ongoing support.
C11. Monitor adoption, use, user feedback, service performance, operational issues, and business outcomes following implementation.
C12. Lead or support reviews following implementation and recommend corrective actions, process improvements, or future product enhancements.
10% D. Facilitate stakeholder engagement, communication, decision making, and organizational change.
D1. Identify internal and external stakeholders and assess their interests, responsibilities, influence, communication needs, and readiness for change.
D2. Build effective working relationships with executives, program leaders, operational teams, technical staff, vendors, frontline users, and external partners.
D3. Facilitate requirements sessions, process design workshops, product discussions, decision meetings, demonstrations, and issue resolution sessions.
D4. Present complex business, technical, data, and product information clearly to technical and nontechnical audiences.
D5. Prepare decision documents, options analyses, recommendations, presentations, reports, dashboards, and stakeholder communications.
D6. Facilitate resolution of competing requirements, conflicting priorities, unclear ownership, and stakeholder disagreements.
D7. Assess how proposed changes will affect business processes, roles, policies, data, reporting, training, and support.
D8. Support stakeholder engagement, communication, training, adoption, and organizational change activities.
D9. Promote user participation, transparency, accountability, and timely decision making throughout the initiative.
D10. Serve as a liaison between business stakeholders and technical teams to ensure a shared understanding throughout delivery.
10% E. Ensure that business and product requirements address public health, regulatory, data, security, privacy, and accessibility needs.
E1. Work with public health, healthcare, government, community, or other regulated program stakeholders to understand program requirements, reporting obligations, service delivery needs, and desired outcomes.
E2. Incorporate applicable privacy, security, accessibility, data governance, records management, and regulatory requirements into business and product documentation.
E3. Identify business requirements associated with confidential, proprietary, personal, and health information.
E4. Coordinate with privacy, security, legal, procurement, data governance, and compliance representatives as necessary.
E5. Analyze data definitions, data quality, data ownership, reporting requirements, interfaces, and information exchanges.
E6. Promote accessible, equitable, and user centered solutions for diverse populations and users with varying levels of technical ability.
E7. Coordinate with epidemiology, informatics, laboratory, surveillance, emergency response, clinical, community program, or population health teams when applicable.
E8. Support initiatives involving governance across multiple agencies, grant requirements, public sector procurement, external reporting, or formal approval processes.
E9. Ensure that required compliance reviews, approvals, documentation, and corrective actions are incorporated into solution delivery.
MINIMUM TRAINING AND EXPERIENCE
• Bachelor's degree in business administration, public health, information systems, technology, healthcare administration, or a related field, or equivalent professional experience.
• Seven or more years of progressively responsible business analysis experience supporting complex software or digital transformation initiatives.
• Three or more years of product management, product ownership, or comparable product delivery experience.
• Demonstrated experience eliciting, documenting, validating, and managing complex business and system requirements.
• Demonstrated experience creating process maps, workflows, use cases, user stories, business rules, acceptance criteria, and requirements traceability documentation.
• Experience supporting software delivery from discovery through testing, implementation, stabilization, and transition to operations.
• Experience working with teams from multiple business areas, external vendors, senior stakeholders, technical personnel, and end users.
• Experience leading or coordinating user acceptance testing, implementation readiness, process change, training, or adoption activities.
Skill SetRequirements:
KNOWLEDGE, SKILLS, AND ABILITIES
1.Extensive knowledge of business analysis principles, practices, techniques, and professional standards.
2.Extensive knowledge of requirements elicitation, analysis, documentation, validation, prioritization, management, and traceability.
3.Extensive knowledge of product management practices, including product vision, roadmaps, discovery, backlog management, prioritization, user stories, acceptance criteria, and lifecycle management.
4.Considerable knowledge of process analysis, process mapping, workflow design, business rules, decision modeling, gap analysis, and continuous improvement.
5.Considerable knowledge of software development and implementation lifecycles, including Agile, Scrum, hybrid, and traditional delivery methods.
6.Knowledge of software design, configuration, integration, data migration, testing, deployment, stabilization, and operational support.
7.Knowledge of user centered design, user research, usability, accessibility, and product adoption practices.
8.Knowledge of testing practices, including test planning, test case development, user acceptance testing, defect management, and requirements validation.
9.Knowledge of data analysis, data definitions, data quality, data governance, reporting, interfaces, and information exchange requirements.
10.Knowledge of project management, risk management, issue management, change control, and dependency management.
11.Knowledge of organizational change, stakeholder engagement, communication, training, and adoption practices.
12.Knowledge of public health, healthcare, government, or other regulated