A failed method costs you a month. Sometimes two.
I learned that on a crisaborole project at Diteba.
Crisaborole is the active in proprietary formulation, the topical eczema ointment. The work was an in-vitro permeation test (IVPT): you mount skin on a Franz cell, apply the ointment, and measure how much drug crosses through. The LC-MS/MS method on the front end has to quantify what made it across.
Method development went clean. Standards looked sharp. Linearity tight. Recovery on spiked controls was where you’d want it. I signed off and we went into validation.
Validation failed on reproducibility. The same sample, run two days apart, gave different numbers. Not within acceptable variance. Different.
We pulled the data apart for a week before we found it. The crisaborole was degrading in the receptor fluid. Not in the standard solutions. Not in the mobile phase. In the actual matrix the IVPT generates. The standards had been lying to us because standards never sit in real matrix for the time real samples do.
The fix was extra steps in the sample handling procedure: forced degradation, tighter time windows between collection and injection, new internal standards we had to custom order. The whole thing added more than a month to the project. The chemistry was always going to work. The method developer (me) hadn’t accounted for what the sample would do to itself while waiting for the autosampler.
That’s the thing most analytical chemists get wrong about this work. Method development isn’t finished when the standards elute cleanly. It’s finished when you’ve asked every question that validation is going to ask later, and answered each one before validation has a chance to find them for you.
Method development is risk mitigation
Most analytical chemists treat method development like a recipe. Get the standards to elute. Get the calibration curve. Move to validation. Done.
That’s not method development. That’s getting a chromatogram.
Method development is the work of asking, before validation, every question that validation is going to ask later. What happens at the upper concentration boundary? What happens at the lower? What happens when you change analysts? What happens when the column has 800 injections on it instead of 80? What happens when the sample sits on the bench for four hours because someone got pulled into a meeting?
If you haven’t stressed the method against those questions, you haven’t developed it. You’ve drafted it.
The cost of skipping this work doesn’t show up during development. It shows up during validation, when the deadline is fixed and the only variable left is your weekend.
The chemistry you have to know before you touch the instrument
Three failures show up over and over. Not because the chemistry is hard. Because people skip it.
The pKa trap is the most common. Every ionizable compound has a pKa, the pH at which half the molecule is ionized and half isn’t. If your mobile phase pH is within 2 units of the analyte’s pKa, you’re running the method in the transition zone. Small pH drift means big retention drift. Peaks ghost. Peaks split. Reproducibility dies. The fix is not exotic: pick a mobile phase pH at least 2 units away from every pKa in your analyte. If the molecule has three pKa values, you have a constraint problem to solve before you weigh out the first buffer salt. I’ve watched analysts spend two weeks chasing peak shape problems that a 10-minute pKa check would have prevented. On one pharmaceutical QC project I audited, the method had been running in production for months with the mobile phase pH sitting 1.2 units from the compound’s secondary pKa. The data looked fine until ambient temperature dropped in winter and the instrument lab ran slightly cooler. Retention time shifted 0.4 minutes across 60 injections. Nobody caught it because nobody had asked the pKa question at the start.
The C18 default is the second. C18 is the most-used reversed phase column on earth. It’s also the wrong choice more often than people admit. If your analyte is highly hydrophobic (logP above 4 or so), C18 will hold it too long and you’ll be running 80% acetonitrile just to elute. If your analyte is polar (logP below 1), C18 won’t hold it at all and you’ll see no retention. If your analyte has strong aromatic character, a phenyl-hexyl column will give you selectivity C18 can’t. If your analyte is genuinely hydrophilic, you should be looking at HILIC. The analyte tells you which column to use. You don’t pick a column and hope the analyte cooperates. I covered the HILIC case in detail in my Acetyl Hexapeptide-8 piece, which is a clean example of what happens when you let the logP make the column decision instead of defaulting to C18.
The scouting gradient gets skipped because it feels redundant. It isn’t. A 5% to 95% organic gradient over 40 to 60 minutes tells you whether you need isocratic or gradient elution (if your peaks span less than a quarter of the gradient time, isocratic is viable), where the impurities elute relative to the analyte, whether the matrix has interferences you didn’t know about, and whether the column is right. That’s four decisions resolved in one run. On the crisaborole project, the scouting gradient was fine. The problem was downstream of chromatography entirely. But on a natural health product project at Canadian Analytical Laboratories, the scouting gradient showed a matrix interference sitting directly under the analyte peak at the pH the method was written for. We shifted pH by 1.2 units and the interference moved cleanly. Forty minutes of scouting saved what would have been weeks of troubleshooting in validation.
What I should have done on the crisaborole project
I should have asked one question I didn’t ask: what does the analyte do in the matrix during the time between sample collection and injection?
Stability is not a validation parameter you check after the method is built. It’s a development question you answer before you write the protocol. A two-hour bench-stability check on a fresh receptor-fluid sample would have caught the degradation in week one instead of week six.
Validation is where you prove problems aren’t there. If validation is finding them instead, the development phase was too short.
Before you touch the instrument
Spend two hours with the chemical structure. Print it. Mark every ionizable group. Look up every pKa. Calculate or look up the logP. Identify every functional group that could degrade: esters, amides, boron compounds (looking at you, crisaborole), thiols, anything photo-sensitive.
Then ask, on paper, what each one of those features means for your mobile phase choice, your column choice, your sample handling, and your storage conditions.
If you can’t answer those questions about your analyte, you’re not ready to make mobile phase. You’re ready to read.
Questions about this framework? You can reach me at hello@nalam.ca or on LinkedIn.