Meet the people accountable for the work.

The people behind the work

Joseph Duddy

Technology, Engineering & Modernization

Joseph leads technology, engineering and modernization, translating business needs into practical systems and improvements.

He approaches the work with respect for the people who already keep the business running. A process may look inefficient from the outside while containing years of experience, necessary workarounds and knowledge that should not be lost. Understanding that context comes before recommending change.

Joseph's responsibility is to make the technical choices understandable: what can stay, what needs attention, what the alternatives involve, and where uncertainty remains. He considers the effect on staff, customers, daily operations and the people who will support the result, not just whether the technology can be built.

What this means for you

• Understand before changing: Learn from the people doing the work and preserve useful knowledge.
• Explain the tradeoffs: Make recommendations, limitations and practical consequences understandable.
• Design for the people using it: Consider disruption, training, support and handover alongside technical capability.

His background spans enterprise infrastructure, communications, cloud platforms, data engineering, automation, and applied AI across healthcare, government, and business environments.

Javier Guevara

Client Outreach & Customer Experience

Javier leads client outreach and customer experience, helping people understand how Adaptiv Stratum can support their business and what working together would involve.

He starts by listening: what is difficult today, what the customer hopes to improve, and what concerns they have about making a change. His role is to help turn those conversations into clear expectations, practical next steps and a relationship built on respectful communication.

During an engagement, Javier helps bring customer questions, feedback and concerns into the conversation with the delivery team. The aim is for customers to feel heard and informed, not passed from one conversation to another without context.

What this means for you

• Listen and understand: Learn what matters to the customer before discussing solutions.
• Keep expectations clear: Help explain the proposed work, next steps and responsibilities.
• Represent the customer's perspective: Bring feedback and concerns into delivery discussions.

His approach combines relationship-driven sales leadership, personalized coaching, and team development, with an ethical entrepreneurial mindset.

The operating reality shapes the engineering.

• Systems & consequence: availability, accurate information, and recovery matter when people depend on the result.
• Infrastructure & continuity: dependencies, identity, and support responsibilities continue after launch.
• Data & applied intelligence: provenance, permissions, and review remain essential as automation expands.

Principles made practical

What clients can expect.

Technology should serve the business and the people who depend on it. Clear communication, respect for existing work and understandable choices matter alongside reliable engineering. These principles guide the responsibilities agreed for each engagement.

Space to explain the problem

You do not need technical terminology to describe what is difficult. We start with the people doing the work, their questions and what needs to improve.

Respect for what already works

Consider staff experience, current investments and useful processes before recommending replacement. Changes should account for disruption and practical dependencies.

Clear, honest explanations

Explain options, tradeoffs and limitations in business language. Distinguish verified findings from assumptions and questions that still need investigation.

A way to raise concerns

Agree who to contact and how questions, feedback and unresolved issues are brought into the work. People retain responsibility for decisions and approvals.

A manageable transition

Consider training, access, support, recovery and handover alongside technical capability, with responsibilities and the agreed scope made clear.

A project-specific combination

People lead. Specialists and AI extend the work.

The partners provide leadership within the agreed engagement. Additional independent specialists are selected when the assignment needs their experience or capacity; sourcing networks are not a standing project team.

AI advisors can organize approved information, compare options, and challenge assumptions. They do not take ownership of engagement objectives, acceptable consequences, or final decisions. Application controls and authoritative systems enforce permissions and approved actions.

Agreement among agents is not proof: shared evidence and assumptions can produce shared mistakes. People remain accountable for verification, approvals, and decisions.

Engineering stewardship

Use technology deliberately.

Respect client capital, existing investments, information, physical resources, and people’s time. Use the simplest architecture that satisfies the need and its controls.

These are decision principles, not a claim of measured environmental savings. Define a defensible baseline and an operating decision before claiming an efficiency benefit.

Accountability on an engagement

From the first question to the handover.

Agree the scope and responsibilities before proceeding, then test the work against the intended outcome. The review follows six connected responsibilities.

1. Understand

   Define the operating problem with the people who know the work. Establish the objective and the decision owner.

2. Challenge

   Use research, data, engineering analysis, and specialist review to test assumptions and expose alternatives.

3. Decide

   A responsible human weighs the tradeoffs and determines which recommendation should proceed.

4. Control

   Bound consequential authority through permissions, business rules, verification, and approval.

5. Verify

   Test implementation against agreed outcomes, including exceptions, recovery, and unresolved limitations.

6. Transfer

   Leave documentation, ownership, access arrangements, and operating knowledge with the client.