Bus Org Readiness Project Manager

We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. Let's parse the posting. We have: - Alternate Locations: list of locations. - Work Arrangement: Hybrid: Employee will work 3 days a week in a Lincoln office. - Relocation assistance: is not available. - Requisition #: 76596 (metadata, drop) - The Role at a Glance: description. - What You'll Be Doing: list of duties (responsibilities). - What We’re Looking For: Must-haves and Nice to haves (requirements/qualifications/skills). - Application Deadline: date (maybe not needed? It's metadata but could be considered? The instruction: remove application instructions. Application deadline is maybe considered application instruction? It's not instruction but still metadata. Probably drop. - What’s it like to work here?: description (maybe About the role? Actually "What’s it like to work here?" is company culture; could be part of About the role? But we have a section "About the role" maybe we can put that description there. However we already have "The Role at a Glance" which is about the role. We could treat that as About the role. - What’s in it for you: list of benefits (career tracks, leadership development, PTO, 401K, counseling, tuition assistance, work arrangements, productivity tools). That's Benefits. - The pay range: Pay section. - About The Company: could be About the role? Actually it's about company; maybe we could include as About the role? But we already have About the role from The Role at a Glance. The instruction: Use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About the role: Could combine "The Role at a Glance" and maybe "What’s it like to work here?"? But "What’s it like to work here?" is more about company culture; still could be part of About the role. However we must not repeat job title as heading. We'll produce an

About the role

with paragraphs describing the role and maybe company culture. - Responsibilities: from "What You'll Be Doing" bullet list. - Requirements: Must-haves (experience, degree, communication skills, problem solver, relationship management). Could be Requirements. - Qualifications: Could be Nice to haves? Or we could treat Must-haves as Requirements, Nice to haves as Qualifications or Skills. The instruction includes both Requirements and Qualifications as possible headings. We need to decide. Usually Requirements = mandatory, Qualifications = preferred. Skills could be separate. But we have both Must-haves and Nice to haves. We could put Must-haves under

Requirements

and Nice to haves under

Qualifications

. Or we could put Skills under Nice to haves. But we have also "Strong communication skills..." etc which are skills. Might be better to put Must-haves as Requirements, Nice to haves as Qualifications, and maybe Skills separate? However we have limited distinct categories. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But they said use headings for those if content exists. We have both mandatory and nice-to-haves; we could make two sections: Requirements and Qualifications. That's fine. - Benefits: from "What’s in it for you". That's Benefits. - Pay: from pay range. - Schedule: from Work Arrangement: Hybrid: Employee will work 3 days a week in a Lincoln office. That's schedule info. - Locations: Alternate Locations list. Could be part of About the role? Or maybe we could add a section? Not in list of allowed headings. Could embed in About the role paragraph. - Relocation assistance: not available. Could be part of Benefits? Or maybe drop as it's negative. Could include in Benefits? But it's not a benefit; it's a statement that relocation assistance is not available. Could be omitted as it's not a positive benefit. The instruction: remove boilerplate; but this is specific info. Could include in a short paragraph under About the role or maybe under Benefits as "Relocation assistance: not available". However Benefits section should only be emitted if posting actually states them. It does state relocation assistance is not available, which is a statement about benefits. Could include but it's not a benefit. Safer to omit. - Application Deadline: drop. - The Role at a Glance: we used for About the role. - What’s it like to work here?: we can incorporate into About the role. Now we need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from those sections. Let's extract specifics. About the role: We'll combine: "The Role at a Glance: We are excited to bring on a Business Organizational Readiness Project Manager to our Retirement Plan Services Change Management Team. In this position you will be responsible for the success of operational change and adoption (business processes) of new or enhanced systems projects or programs with a business emphasis. You will lead activities to ensure that tasks such as training, communication, marketing, documentation, and processes/procedures are accomplished within the project timelines to enable milestones for complex projects, including efforts to launch new products and services, large scale application development, systems integration, operational efficiency improvements, process reengineering, and infrastructure upgrades and deployments. You will have a great deal of interaction with teams and individuals at all levels within the organization. We are looking for a highly energized and motivated individual to grow with our team and help drive value." Then "What’s it like to work here?: At Lincoln Financial, we love what we do. We make meaningful contributions each and every day to empower our customers to take charge of their lives. Working alongside dedicated and talented colleagues, we build fulfilling careers and stronger communities through a company that values our unique perspectives, insights and contributions and invests in programs that empower each of us to take charge of our own future." We could combine into one or two paragraphs. Responsibilities: list from "What You'll Be Doing". Let's capture each bullet: - Partners closely with the Portfolio Owner and Product Manager to understand objectives and key results and identifies and partners with key stakeholders to ensure organizational readiness - Works on more complex initiatives spanning across business areas, and develops appropriate plans to ensure organizational readiness activities are executed to prepare for milestones - Coordinates, documents, and leads readiness activities and processes with cross-functional support teams ensuring successful delivery of initiatives, focused on impact analysis, business adoption, preparedness and execution - Aligns org readiness activities to Portfolio roadmaps - Identifies key cross-functional issues and initiative synergies; provides guidance with specific initiative issues - Collaborates effectively with Portfolio/Value Streams, management and appropriate stakeholders on more complex issues and conflicts that impact time, cost, scope, quality and risk of assigned initiatives - Analyzes assigned initiative plans to validate if outcomes will meet the business needs and align/support operational plans/objectives and recommends mitigation plans - Identifies more complex initiative resourcing needs and facilitates the procurement of needed hardware, software, and human resources for the project - Monitors and evaluates assigned more complex initiative progress and performance against the project plan and develops more complex mitigation plan We need to preserve all detail; we can put each as

. Requirements (Must-haves): - 3-5+ Years of experience in project management, change management, or business analysis that aligns with the specific responsibilities for this position - 4 Year/Bachelor's degree or equivalent work experience (4 years of experience in lieu of Bachelor's) - Strong communication skills with ability to influence and negotiate both vertically and horizontally to obtain or leverage necessary resources - Able to articulate enterprise strategies and priorities - Strong problem solver with ability to lead the team to push the solution and progress - Strong relationship management skill We need to keep exact phrasing. Qualifications (Nice to haves): - Working knowledge of Retirement Plan Services products, processes, goals and measures - Working knowledge of the business function/industry trends, user demands and pain points - Risk and compliance focused - Lean Six Sigma, DMAIC, or Continuous Improvement experience - Demonstrated curiosity and proficiency in adopting AI tools to improve work processes, generate insights, drive continuous improvement Benefits (What’s in it for you): - Clearly defined career tracks and job levels, along with associated behaviors for each of Lincoln's core values and leadership attributes - Leadership development and virtual training opportunities - PTO/parental leave - Competitive 401K and employee benefits - Free financial counseling, health coaching and employee assistance program - Tuition assistance program - Work arrangements that work for you - Effective productivity/technology tools and training Pay: The pay range for this position is $84,375 - $135,000 with anticipated pay for new hires between the minimum and midpoint of the range and could vary above and below the listed range as permitted by applicable law. Pay is based on non-discriminatory factors including but not limited to work experience, education, location, licensure requirements, proficiency and qualifications required for the role. The base pay is just one component of Lincoln’s total rewards package for employees. In addition, the role may be eligible for the Annual Incentive Program, which is discretionary and based on the performance of the company, business unit and individual. Other rewards may include long-term incentives, sales incentives and Lincoln’s standard benefits package. Schedule: Work Arrangement: Hybrid : Employee will work 3 days a week in a Lincoln office. Locations: Alternate Locations: Charlotte, NC (North Carolina); Fort Wayne, IN (Indiana); Omaha, NE (Nebraska); Radnor, PA (Pennsylvania). Could be included in About the role or maybe a separate section? Not in allowed headings; we can embed in About the role paragraph. Relocation assistance: is not available for this opportunity. Could be omitted or maybe include in Benefits as a note? But it's not a benefit; it's a lack. Probably drop as it's not a benefit and not required to preserve? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should preserve that piece. Where to put? Could add a short paragraph under Benefits? But Benefits section should only be emitted if posting actually states them. It does state relocation assistance is not available, which is a statement about benefits (lack thereof). Could include as a sentence: "Relocation assistance is not available for this opportunity." That is substantive. We'll include it maybe in a

under Benefits or under About the role. Since Benefits section already exists, we can add that sentence there. Application Deadline: drop. Now we need to output HTML fragment only, no /, no markdown. We'll produce:

About the role

... combined paragraphs ...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

• ...
...

Relocation assistance is not available for this opportunity.

Pay

... pay details ...

Schedule

Hybrid: Employee will work 3 days a week in a Lincoln office.

We need to ensure we don't repeat job title as heading. Not using. Check for any boilerplate: EEO, equal opportunity, scam warning, etc. We removed. Now verify we preserved all substantive info from sections we used. Let's extract each piece and ensure included. From "The Role at a Gl