Job Description

Job Description

Delivery Lead

\n

\n

Purpose of the Role

\n

\n

At UnderStory, we believe sustainable delivery starts with people, is supported by the right process, and is enabled by technology.

\n

\n

The Delivery Lead brings that philosophy into our client work every day.

\n

\n

This is a leadership role responsible for creating the conditions in which clients and delivery teams can do their best work. The Delivery Lead owns the details of delivery and the day-to-day connection between UnderStory, the client, and the delivery team for technical implementations.

\n

Success requires more than managing a plan. It means building trust, creating clarity and accountability, recognizing where teams need support, and introducing the right amount of structure to keep work moving.

\n

\n

The Delivery Lead brings a broad toolkit across traditional project management and Agile delivery, but is not attached to a particular methodology. They know when a detailed project plan is useful, when a backlog or iterative approach makes more sense, when a meeting is necessary, and when process is simply getting in the way.

\n

\n

What You'll Own

\n

\n

\n
• Lead the day-to-day delivery of technical implementation engagements.
\n
• Build strong, trusted relationships with client stakeholders and delivery team members.
\n
• Create clarity around goals, priorities, responsibilities, decisions, and commitments.
\n
• Maintain visibility into scope, milestones, dependencies, risks, blockers, and progress.
\n
• Establish delivery rhythms and practices appropriate to the work and the people doing it.
\n
• Serve as the primary day-to-day connection between the client and UnderStory delivery team.
\n
• Surface difficult issues early and help the right people work through them.
\n
• Facilitate planning, prioritization, decision-making, status conversations, retrospectives, and other working sessions when they add value.
\n
• Coordinate across technical, product, business, external partner, and client stakeholders.
\n
• Help teams make realistic commitments and follow through on them.
\n
• Protect teams from unnecessary process while adding structure where it improves delivery.
\n
• Help clients build stronger delivery capability through the work we do together.
\n

\n

\n

How You'll Work

\n

\n

People First

\n

\n

Strong delivery starts with the people doing the work.

\n

\n

You'll pay attention to communication, relationships, ownership, team dynamics, and the conditions people need to succeed. You'll build trust with clients while being willing to surface uncomfortable truths, challenge assumptions, and address problems before they become delivery failures.

\n

\n

The Right Process

\n

\n

Process should help people deliver, not become the work itself.

\n

\n

You may use project plans, backlogs, RAID logs, milestones, sprints, Kanban boards, stand-ups, status reports, retrospectives, or other tools.

\n

\n

We care less about which tools you use than whether you understand why you're using them.

\n

You'll adapt the approach to the engagement rather than forcing the engagement into a methodology.

\n

\n

Technology in Context

\n

\n

You don't need to be the person writing the code, but you need to be comfortable leading technical work.

\n

\n

You'll work closely with engineers and technical leaders to understand dependencies, risks, tradeoffs, and constraints well enough to help the team and client make good decisions.

\n

Technology enables the outcome. It is not separate from the people and processes required to deliver it successfully.

\n

\n

What Success Looks Like

\n

\n

\n
• Clients and delivery teams trust one another and have clarity about what they own.
\n
• People have the information and context they need to make good decisions.
\n
• Risks, dependencies, and misalignment become visible before they become emergencies.
\n
• Commitments are realistic and progress is transparent.
\n
• The work has enough structure to create accountability and predictability without unnecessary bureaucracy.
\n
• Technical complexities and tradeoffs are understood and communicated clearly.
\n
• Delivery practices evolve as the needs of the engagement evolve.
\n
• The client is stronger and more capable because UnderStory was there.
\n

\n

\n

What We're Looking For

\n

\n

\n
• Experience leading complex software, technology, or technical implementation work.
\n
• Strong client-facing leadership and communication skills.
\n
• Experience working closely with engineers and technical teams.
\n
• Working knowledge of both traditional project management and Agile delivery approaches.
\n
• A broad delivery toolkit and the judgment to know what to use, when to use it, and when to leave it behind.
\n
• Ability to move comfortably between delivery details and the larger outcome.
\n
• Confidence navigating ambiguity, competing priorities, changing conditions, and difficult conversations.
\n
• Strong instincts around team dynamics, communication, and accountability.
\n
• A bias toward ownership, transparency, practicality, and action.
\n

\n

\n

Engagement Structure

\n

\n

This role is expected to begin as an independent consulting engagement dedicated to an UnderStory client engagement. The scope will be tied to the duration and needs of that project, with no guarantee of permanent employment or a long-term direct-hire commitment from UnderStory.

\n

\n

This is expected to be a part-time engagement averaging approximately 20 hours per week. Actual weekly hours may vary based on project phase, client needs, meeting cadence, and delivery priorities.

\n

\n

The work will include a mix of remote and onsite participation. Because some onsite client and team work is expected, the ideal candidate will be located in the Rochester, NY area or within a reasonable driving distance.

\n

\n

The consultant will be expected to participate in relevant client and team meetings, manage agreed delivery responsibilities, and meet defined commitments and deadlines. Outside of those requirements, they will have flexibility in how and when the work is completed.

\n

\n

Candidates who already operate independently through an LLC, DBA, or similar business structure are preferred.

\n

Job Tags

Permanent employment, Part time, Remote work

Similar Jobs