Why Small Biotechs Combine Quality and IT

Most early biotechs do not decide to combine quality and IT. It happens over time. The company signs its first contract manufacturer, picks an electronic document management system, adds an eQMS module, and starts a Phase 1 study with a CRO that hosts the electronic data capture system. Somebody has to own those systems from the sponsor side. The person who understands validation, change control, and audit trails is usually the head of quality, so the systems go to that person. A year later, the same person is also approving laptop purchases, managing the managed service provider, and fielding questions about multi-factor authentication.

The other path runs the opposite way. A company hires a technology leader first, often someone with a strong infrastructure or data background, and asks them to cover quality systems as well until a quality hire is made. That hire gets delayed, and the technology leader ends up writing SOPs and approving deviations.

Both paths are understandable. In a small company there are only so many senior roles, and both functions share a vocabulary of controls, records, and procedures. The problem is not that one person is doing too much. The problem is what that person is doing to their own work.

The Four Shapes This Usually Takes

When we look at how small biotechs have arranged these two functions, four shapes come up again and again. They carry very different levels of independence risk.

Shape 1

One Person, Two Titles

A single leader is head of quality and head of IT. They approve SOPs, own GxP systems, manage the IT provider, and sign off on changes. The highest independence risk, and the most common in companies under fifty people.

Shape 2

IT Reports to the Head of Quality

A separate IT manager or service provider does the technical work but reports to quality. Independence risk is moderate. Quality is approving work done by its own team, but at least the hands that make the change and the hand that approves it differ.

Shape 3

Quality Reports to a Technology or Operations Leader

The head of quality reports to a COO, CTO, or head of technical operations who also owns IT. This puts quality under the person whose systems and schedules it oversees. Often the hardest shape to defend, because the conflict is built into the reporting line rather than into a task.

Shape 4

Quality Leader With an Outsourced IT Function

The head of quality owns GxP system oversight, but infrastructure and administration sit with an external provider under a written agreement. Independence risk is lowest of the four, and this is often where a well-run combined role should be heading.

Shape 3 deserves a word of caution. Leaders sometimes treat it as the safer option because quality has its own head. But if that head of quality depends on a technology or operations executive for budget, priorities, and performance reviews, the quality function’s authority over that executive’s systems is weaker than it looks on the organization chart. The rest of this article focuses mostly on Shapes 1 and 2, because those are the ones small biotechs ask about, but the safeguards apply to all four.

What the Regulations Say About Independence

It helps to be exact about what the rules require, because conversations about this topic tend to swing between two wrong positions. One is that the regulations forbid a quality leader from running IT. They do not. The other is that, because they do not forbid it, there is nothing to manage. That is also wrong.

The Quality Unit Must Have Authority

US CGMP rules for finished pharmaceuticals require a quality control unit with the responsibility and authority to approve or reject components, in-process materials, labeling, and drug products, and to review production records. The same section states that this unit is responsible for approving or rejecting drug products made, processed, packed, or held under contract by another company, and that its responsibilities and procedures must be written down and followed.1 For a virtual or mostly outsourced biotech, that contract clause matters most. Handing manufacturing to a CDMO does not hand over the approval decision.

Part 211 also requires that written production and process control procedures, including any changes, be “drafted, reviewed, and approved by the appropriate organizational units and reviewed and approved by the quality control unit.”2 That sentence describes two separate acts: the function that owns the work drafts and approves, and quality reviews and approves. When one person is both, the two acts collapse into one.

Independence Is Expected Between the Quality Unit and the Work It Oversees

ICH Q10, the harmonized model for a pharmaceutical quality system, tells management to define the roles, responsibilities, and authorities of all units related to the quality system, and notes that “An independent quality unit/structure with authority to fulfil certain pharmaceutical quality system responsibilities is required by regional regulations.”5 The EU GMP chapter on personnel is more specific. It states that “The heads of Production and Quality Control must be independent from each other,” and it requires an organization chart that clearly shows the relationships between those heads.6

The same EU chapter includes a line that is directly relevant to a combined role, even though it never mentions IT: “The responsibilities placed on any one individual should not be so extensive as to present any risk to quality.”6 That is a test of workload and conflict, not a ban on combining jobs.

Other GxP areas set the bar higher. The US good laboratory practice rule for nonclinical studies requires that, for any given study, the quality assurance unit be “entirely separate from and independent of the personnel engaged in the direction and conduct of that study.”3 Most small biotechs run their nonclinical studies at contract research organizations, so this requirement falls mostly on those testing facilities. It is still a useful reminder of how strictly regulators can define independence when they choose to.

The Exception FDA Already Wrote Down

The most useful single source on this question is FDA’s 2006 guidance on the quality systems approach to CGMP. It says that under a quality system, the development units, the manufacturing units, and the quality unit are normally expected to remain independent. It then adds: “In very limited circumstances, a single individual can perform both production and quality functions.” That person stays accountable for the controls and for reviewing the results. The guidance continues: “Under such circumstances, it is recommended that another qualified individual, not involved in the production operation, conduct an additional, periodic review of QU activities.”4

That guidance is about production and quality, not IT. But the reasoning carries over cleanly. When one person must hold two roles that should be independent, the answer FDA describes is not to pretend the conflict away. It is to add a second, qualified person who was not involved in the work and who reviews it on a schedule. That is the backbone of every safeguard later in this article.

System Administration Is Treated as a Conflict of Its Own

For computerized systems, regulators have been specific about one particular conflict. FDA’s compliance program for prelicense and preapproval inspections of CDER-regulated biological products, issued in April 2026, tells the inspection team to “Verify that the system administrator role and any rights to alter files and settings are assigned to personnel independent from those responsible for the record content and verify that the quality unit maintains and controls a list of authorized individuals for each system.”8 The UK MHRA’s GxP data integrity guidance says the same thing in more detail: “System Administrator rights (permitting activities such as data deletion, database amendment or system configuration changes) should not be assigned to individuals with a direct interest in the data (data generation, data review or approval).”9 MHRA also asks companies to keep administrator access to the smallest number of people possible given the size and nature of the company, and explains that the point is to keep people with a possible conflict of interest from making changes that cannot be traced to them.9

This is where a combined quality and IT role runs into the most concrete trouble. A head of quality who approves records in the eQMS and also holds the administrator account for that eQMS is in exactly the position both regulators describe.

85 FDA warning letters to drug product manufacturers posted January 1 to December 9, 2025, reviewed in one published analysis14
54 Citations of 21 CFR 211.22, 211.22(a), and 211.22(b) in those letters, which the authors describe as inadequate quality unit authority and responsibilities14
1 Additional qualified reviewer FDA recommends when one individual performs both production and quality functions4

What Inspectors Write When Independence Is Missing

FDA warning letters show what this looks like when it goes wrong. In a January 2020 letter to a drug manufacturer, FDA wrote that the firm had failed to establish an independent and effective quality unit, and added: “Your QU was also not independent from the manufacturing unit.” The example given was that the factory director, “responsible for manufacturing operations, was also acting as the Quality Director.”12 That case involved production rather than IT, and the firm had many other problems. But it shows that inspectors do look at who holds which title, and that one person in two conflicting roles is something they name in writing.

Outsourcing does not make this go away. In an August 2026 warning letter to a company that held, labeled, released, and distributed over-the-counter drugs made by contract manufacturers, FDA recorded that “you stated that no QU oversight is performed for your suppliers and contract manufacturers, including packagers.” The letter also restates a long-standing position: “FDA regards contractors as extensions of the manufacturer.”13 For a biotech that outsources almost everything, the quality function’s job is oversight. If that oversight is performed by the same person who owns the systems being overseen, the company needs to be able to show how the conflict is controlled.

When Combining the Roles Works

A combined quality and IT role is not a mistake in itself. In the right conditions it gives a small company something valuable: one senior person who understands both what the regulations expect of a computerized system and how that system is configured and run. The handoff problems between quality and IT that slow validation in larger companies largely disappear when both sides report to the same person. The question is whether the conditions that make the combined role sensible are still true.

Condition One: The Company Is Early and Small

Before a company has its own manufacturing or laboratory operations, the quality function is mostly about oversight. It qualifies and audits vendors, reviews batch records and certificates from the CDMO, approves SOPs, manages deviations and CAPAs (corrective and preventive actions), and keeps the training and document systems in order. The IT function is mostly about provisioning accounts, laptops, collaboration tools, and a short list of SaaS applications. In that setting, the volume of GxP technology decisions is low enough that one leader can make them carefully, and an independent reviewer can check the important ones without becoming a bottleneck.

Condition Two: There Are Few GxP Systems

The number of computerized systems that hold GxP records is a better guide than headcount. A company with an eQMS, an electronic document system, a learning management system, and a CRO-hosted EDC system has a short, stable list. The combined leader can know every one of them well. When that list grows to include a LIMS, an environmental monitoring system, an ERP with GxP functions, and several clinical systems hosted by the company itself, the number of changes, access requests, periodic reviews, and validation packages rises quickly. Each one is a point where the leader may be approving their own work.

Condition Three: Operations Are Outsourced

When the CDMO, the CRO, and the SaaS vendors run the systems that generate primary GxP data, much of the day-to-day conflict moves outside the company. The vendor’s staff administer the platform. The CDMO’s quality unit approves its own changes. The sponsor’s combined leader is reviewing and approving the vendor’s work rather than their own. That is a much easier position to defend.

There is a limit to this. FDA’s guidance on quality agreements is clear that “quality agreements cannot be used to delegate statutory or regulatory responsibilities to comply with CGMP.”11 ICH Q10 says the same thing in management terms: the pharmaceutical company is ultimately responsible for making sure processes are in place to control outsourced activities.5 Outsourcing reduces the number of places where the combined leader approves their own work. It does not reduce the company’s responsibility to oversee the work it outsourced.

Condition Four: The Leader Has the Right Background

A combined role works best when the person holding it has a quality and validation background and manages IT through a provider, not the other way around. A quality leader who understands computerized system validation and data integrity can direct an IT provider sensibly. A technology leader without quality training who is asked to approve deviations and release decisions is being asked to do work they are not qualified for, which is a separate problem from independence and often a larger one.

A practical test. Write down every GxP system, who administers it, who approves changes to it, and who approves the records it holds. If the combined leader’s name appears in more than one of those columns for the same system, that system needs a safeguard. If it appears in all three for several systems, the combined role is carrying more conflict than safeguards can easily absorb.

Where Independence Breaks Down

The conflicts in a combined quality and IT role are specific. They show up in particular tasks, and naming them precisely makes them much easier to control. These are the ones we see most often.

Approving Your Own Changes

Change control exists so that a person other than the one making a change assesses its impact and agrees it is acceptable before it goes live. In a combined role, the leader often requests a change (for example, a new workflow in the eQMS), directs the IT provider to configure it, writes or approves the testing, and then approves the change for release in their quality capacity. Every step may be documented, and the records may look complete. But no independent person has looked at the decision. An inspector reading the change record will see the same name in the requester, implementer, and approver fields.

Owning and Auditing the Same System

The quality function normally audits computerized systems as part of its self-inspection program. EU GMP is direct about how that should be done: “Self inspections should be conducted in an independent and detailed way by designated competent person(s) from the company. Independent audits by external experts may also be useful.”7 If the combined leader is also the system owner, a self-inspection of that system is the leader reviewing their own decisions. The result may be honest, but it is not independent, and the company cannot show that it is.

Holding Administrator Rights to Systems Whose Records You Approve

This is the conflict regulators have described most clearly, as covered above. In small companies it often starts innocently. The head of quality configured the eQMS during implementation and kept administrator rights afterward because nobody else knew the system. Two years later, that person approves deviations, CAPAs, and document releases in a system where they can also change settings, alter workflows, and, depending on the platform, edit or remove records. Even if they never misuse that access, the company cannot show that they could not have.

Investigating Failures in Systems You Own

When a computerized system fails in a way that affects GxP records (a failed interface, a lost audit trail entry, an access control error), the event should go through deviation management. In a combined role, the leader responsible for the system is also the leader who decides whether the event is a deviation, how severe it is, what the root cause was, and whether the CAPA is adequate. That is the point where an independent view matters most, because the most natural root cause for anyone to reach about their own system is “user error.”

Risk Assessments With a Preferred Answer

ICH Q9(R1) gives decision makers the job of making sure that subjectivity in quality risk management is managed and minimized, and it says that “The level of effort, formality and documentation of the quality risk management process should be commensurate with the level of risk.”10 A combined leader who is also accountable for an IT project’s schedule has an incentive, often unnoticed, to rate a system as lower risk, because lower risk means less validation effort and an earlier go-live. The risk assessment may still be reasonable. The problem is that the person with the incentive is the one deciding.

Competing Objectives in One Calendar

The last conflict is less visible but just as real. A combined leader is measured on IT delivery (systems live, users onboarded, tickets closed) and on quality outcomes (deviations closed, audits passed, inspections without findings). When those collide, the same person decides which wins. In practice, the IT work often has a louder sponsor and a firmer date. Quality reviews wait, or get rushed to meet the IT date.

Conflict Where It Shows Up What an Inspector or Auditor Sees
Approving your own changes Change records for GxP systems The same name as requester, implementer, and quality approver
Owning and auditing the same system Self-inspection program and reports Audits of systems performed by the system owner, with no external or independent check
Administrator rights plus record approval User access lists and audit trails A quality approver holding configuration, deletion, or database rights in the same system
Investigating your own system’s failures Deviations and CAPAs about computerized systems Root causes and CAPA effectiveness checks approved by the person responsible for the system
Risk assessments with a preferred answer Validation plans and system risk classifications Low risk ratings on systems with direct GxP impact, approved by the project lead
Competing objectives Approval queues, overdue reviews Quality reviews consistently late while IT milestones are met

The test is whether you can show it, not whether it happened. Most combined leaders we meet are careful and honest. That is not the standard. The standard is whether the company can show, from its records, that no single person was able to change a GxP system or record and then approve it without another qualified person seeing the decision.

Safeguards That Keep a Combined Role Defensible

None of the conflicts above requires splitting the role on day one. Each can be controlled with a specific safeguard. The six below, taken together, describe a combined role that a small biotech can explain clearly to an inspector, a partner’s auditor, or a potential acquirer.

1

Write the Combined Role Down Honestly

Put both remits in the job description and show them on the organization chart. EU GMP expects an organization chart that shows the relationships between key quality and operations roles, and written job descriptions with adequate authority, with no gaps or unexplained overlaps.6 An overlap that is named and explained is far easier to defend than one an inspector finds on their own.

2

Document Segregation of Duties by System

For each GxP system, record who requests changes, who implements them, who administers the system, who approves records, and who reviews the combined leader’s own actions. NIST defines separation of duty as the principle that “no user should be given enough privileges to misuse the system on their own.”15 A one-page matrix per system turns that principle into something you can show.

3

Route the Leader’s Own Work to an Independent QA Reviewer

Any change, validation deliverable, deviation, or risk assessment where the combined leader was the requester, author, or system owner goes to a second qualified person for quality approval. This follows the pattern FDA described for the one-person production and quality case: another qualified individual, not involved in the work, reviews it.4

4

Move Administrator Rights Away From the Approver

Give system administration to the vendor, the IT provider, or a named person who does not generate, review, or approve the records in that system. The combined leader keeps an ordinary user role for approvals. This applies the FDA and MHRA expectations on administrator independence directly.89 Where the platform cannot support this, document why, and add a periodic review of the administrator audit trail by the independent reviewer.

5

Commission External Audits of the Combined Function

At least once a year, have an external auditor review the computerized systems the combined leader owns and the quality decisions made about them. FDA’s quality systems guidance notes that a periodic review by a qualified source external to the organization may be useful in assessing the suitability and effectiveness of the quality system, and EU GMP names independent audits by external experts as useful for self-inspection.47

6

Give Quality a Direct Line to the CEO

The combined leader should report to the CEO, and quality matters should reach the CEO and the board without passing through anyone with a stake in the IT outcome. ICH Q10 asks management to make sure a timely and effective escalation process exists for raising quality issues to the right level.5 The independent reviewer and the external auditor should also be able to raise concerns directly to the CEO.

A Segregation of Duties Matrix You Can Start From

The matrix below shows a typical allocation for a small biotech with a combined quality and IT leader, an external IT provider, and a part-time independent QA reviewer. Adjust it per system. The important column is the last one: it names the person who checks the combined leader’s work.

Activity Performed By Approved or Reviewed By
Request a change to a GxP system Business process owner or combined leader Combined leader assesses impact; independent reviewer approves if the leader requested it
Configure or implement the change Vendor or IT provider Combined leader verifies against the approved request
Approve validation plans and reports for a system the leader owns Combined leader or validation contractor authors Independent QA reviewer
Administer the system (accounts, configuration, audit trail settings) Vendor or IT provider Independent reviewer checks a sample of administrator audit trail entries each quarter
Periodic user access review Combined leader prepares Independent reviewer signs off, including the leader’s own access
Deviation or CAPA about a computerized system Combined leader or delegate investigates Independent reviewer approves root cause, impact assessment, and CAPA
Risk classification of a new GxP system Combined leader with the business owner Independent reviewer approves the final classification
Self-inspection of computerized systems External auditor or independent reviewer Report goes to the CEO and the combined leader; CAPAs tracked by quality
Qualification of the system vendor Combined leader Independent reviewer for vendors of high-risk systems

Notice what the matrix does not do. It does not take quality decisions away from the combined leader in general. The leader still approves the CDMO’s batch records, the SOPs written by other functions, and the deviations raised in clinical operations. The independent reviewer only takes the decisions where the leader would otherwise be checking their own work. In a small company, that is usually a manageable share of the total.

Keep the Safeguards Proportionate

ICH Q9(R1) asks for effort and formality that match the level of risk.10 The same principle applies here. A change to a report layout in the learning management system does not need the same independent review as a change to the electronic signature workflow in the eQMS. Define, in the change control SOP, which categories of change made by or for the combined leader need independent approval. Then the reviewer’s time goes to the changes that matter, and the arrangement stays workable.

Who Provides the Independent Review in a Small Company

Every safeguard above depends on a second qualified person. In a company of forty people, that person may not exist on the payroll. There are several workable options, and one common choice that does not work.

Options That Work

Option Strengths Watch For
A second quality professional on staff, even part time Knows the company and its systems; available for timely approvals Must not report to the combined leader for the decisions they review, or must have a documented right to escalate to the CEO
A contract QA reviewer under a written agreement Independent of the company’s internal reporting lines; can be scoped to specific decisions Needs enough system knowledge to review meaningfully; response times belong in the agreement
An external auditing firm on an annual or semiannual cycle Clear independence; useful evidence for inspectors and partners Periodic only; does not replace review of individual changes and deviations
A quality leader from a parent, partner, or sister company Strong independence and relevant expertise Confidentiality, contractual authority, and availability need to be written down

Most small biotechs combine two of these. A contract QA reviewer handles the day-to-day independent approvals, and an external auditor reviews the whole arrangement once a year. That pairing gives timely decisions and a periodic independent check, which matches the two kinds of review FDA’s guidance describes: another qualified person reviewing the quality work, and a periodic review by an external qualified source.4

The Option That Does Not Work

The tempting shortcut is to ask the IT provider or the validation contractor to act as the reviewer. They know the systems, they are already under contract, and they are external. But they are not independent of the work. The IT provider implemented the change. The validation contractor wrote the test scripts. Asking them to approve the combined leader’s decisions about their own work replaces one conflict with another.

The same caution applies to the CDMO’s or CRO’s quality unit. Their quality function is responsible for their operations. It is not a substitute for the sponsor’s oversight of those operations, and FDA’s quality agreements guidance makes clear that neither party can delegate its CGMP responsibilities through an agreement.11

What makes a reviewer independent. Three tests: the reviewer did not do the work being reviewed, the reviewer’s pay and performance do not depend on the person whose work they review, and the reviewer has a written right to raise concerns above that person. A reviewer who fails any one of the three is a helper, not a safeguard.

Making the Review Practical

Independent review fails most often because it is slow, not because it is resisted. If the contract reviewer takes two weeks to approve a change, the company starts finding reasons to classify changes as not needing review. Three things help:

  • Agree a response time in the contract. For example, two business days for routine changes and one for urgent ones, with a named backup.
  • Give the reviewer direct access to the systems. A read-only role in the eQMS and document system lets the reviewer see the record, the audit trail, and the history without waiting for someone to export it.
  • Send the reviewer a short monthly list. Every change, deviation, and access change in the systems the leader owns, with a mark against the ones routed for independent approval. The reviewer can then confirm that nothing that should have come to them was missed.

That monthly list does a second job. Over time it shows how much of the reviewer’s work comes from the combined role, which is one of the clearest signals of when the role should be split.

Signals It Is Time to Split the Roles

A combined quality and IT role is a stage, not a permanent design. The safeguards make it defensible for a period, but they also add work, and at some point the work of controlling the conflict becomes larger than the benefit of having one leader. These are the signals we watch for.

Signal Why It Matters
The company brings manufacturing or a QC laboratory in house The company now generates primary GMP data on its own systems. EU GMP requires the heads of production and quality control to be independent, and the volume of system changes and data review rises sharply.6
The list of GxP systems keeps growing Each new system adds changes, access reviews, and validation work. When the independent reviewer is approving a large share of all quality decisions, the safeguard has become the quality function.
A marketing application is in preparation FDA’s 2026 compliance program for prelicense and preapproval inspections of biological products directs inspectors to verify that the quality unit reviews and approves validation protocols and reports, deviations, CAPAs, and change controls, and to check who holds system administrator rights.8 A combined role will need a clear explanation and a clean record of independent review.
The leader has started generating or entering GxP data A leader who creates records, approves them, and owns the system that holds them is in the position MHRA describes as a direct interest in the data.9
Quality approvals wait behind IT work A growing quality review queue while IT milestones are met is the competing-objectives conflict in measurable form.
External audits keep raising the same independence observations Repeat observations mean the safeguards are not holding. A CAPA that keeps reopening is a structural problem, not a procedural one.
A partner, licensee, or acquirer asks pointed questions during due diligence Outside parties often see the arrangement more clearly than people inside it. Their questions are a preview of an inspector’s.

No single signal settles the question. One signal, handled well, may only mean the safeguards need tightening. Two or three together usually mean the company has outgrown the combined role.

Which Way to Split

When the roles separate, the direction matters. The most defensible result keeps the head of quality independent, reporting to the CEO, with authority over the quality decisions for every GxP system. IT moves to a separate leader who reports to the COO, the CFO, or the CEO. Where possible, the new IT leader should not sit above quality in the reporting line, for the same reason Shape 3 is hard to defend.

Some companies split the other way: the combined leader keeps IT and the company hires a new head of quality. That can work, but it needs care. The person who built the systems is leaving the quality role, and the new head of quality will be reviewing systems designed by a peer who knows them far better. Give the new quality leader time and access to review those systems on their own terms before taking over approvals.

Splitting Without Losing What Worked

The combined role usually did one thing well: it kept quality and IT talking. Splitting the role can bring back the handoff problems the company avoided while one person held both. A few steps reduce that risk:

  • Hand over the segregation of duties matrix, not just the systems. It already documents who does what. Update the names and keep using it.
  • Keep the independent reviewer for a transition period. The reviewer knows the history of changes and decisions and can help the new leader get oriented.
  • Agree decision rights between the two new leaders in writing. Who classifies a system’s risk, who approves a vendor, who owns the validation plan. Settle these before the first project under the new structure.
  • Move administrator rights at the same time. A split that leaves the former combined leader with administrator access in systems where they no longer approve records still has an access conflict, just a different one.

What to have ready when someone asks. Whether the question comes from an inspector, a partner’s auditor, or an acquirer’s diligence team, a small biotech with a combined quality and IT role should be able to produce, quickly: an organization chart and job description that show both remits; a segregation of duties matrix for each GxP system; a current user access list showing who holds administrator rights; the agreement with the independent reviewer and a log of decisions routed to them; the last external audit report and the status of its CAPAs; and a short written rationale for the combined role, with the conditions under which the company will split it.

That last item is worth emphasizing. A short statement, approved by the CEO, that explains why the company combined the roles, what safeguards are in place, and which events will trigger a split, shows that the arrangement is a deliberate choice under management control. It turns a question an inspector might treat as a finding into a conversation about a documented decision.

Conclusion

Combining quality and IT leadership in biotech is a reasonable choice at the right stage. When the company is small, its GxP systems are few, and its partners run the operations that generate primary data, one leader who understands both validation and technology can be an advantage. The arrangement becomes a risk when the person who approves changes, records, and risk assessments is also the person who makes those changes and administers those systems, with nobody else in a position to see the decision. The regulations do not ask small companies to hire people they do not need. They ask for an independent quality function with real authority, and for controls that keep any one person from changing a GxP record and then approving it. FDA’s quality systems guidance already describes the pieces: a second qualified reviewer when one person holds two roles that should be independent, and a periodic review by a qualified source outside the company. Written down and kept proportionate, that pattern gives a small biotech a combined role it can defend, and a clear set of signals for when to move on from it.

Sakara Digital works with pharma and biotech organizations deciding how to structure quality and technology leadership as they grow. If you are weighing whether to combine these roles, how to make an existing combined role defensible, or when to split it, we are happy to have that conversation and offer an independent view.

For Further Reading

For Further Reading