You’ve thought about a DBA while working full-time. Then you’ve looked at your calendar — and stopped thinking about it. This is the moment most senior executives quit before they even start. They are not wrong to hesitate. They are wrong about what they should be measuring.
Can You Do a DBA While Working Full-Time? What It Actually Takes
You’ve thought about doing a DBA while working full-time. Then you looked at your calendar and stopped thinking about it. That is where most experienced leaders give up before they start. The hesitation makes sense; it just tends to fix on the wrong number.
The real question isn’t whether you have time. It is whether the program is built so the time you do have actually counts. What follows lays that out with the actual figures, and without pretending the effort is small: what an executive DBA demands week to week, what decides whether you finish, and what a serious program should give you in return.
« I don’t have time » deserves to be taken seriously rather than waved away. It is the most common reason experienced leaders close the DBA conversation before they ever open it. It sounds like a statement about arithmetic. It almost never is.
Look underneath it and what surfaces is rarely a calendar conflict. It is usually something more specific. Fear of overload – of adding one more thing to a life already running at the edge of its capacity. Fear of failing in public – of starting a doctorate and not finishing. Fear of letting your family down – of being absent for an investment they didn’t vote for. Fear of being out of your depth – of finding out, well into a career, that you can’t do the thing you thought you wanted to.
None of these are weak fears. They are the fears of someone who has built a life worth protecting. Naming them won’t make them disappear, but it does make them clearer.
Once they’re named, the real question comes into view. Not « do I have the hours? » but « is the program built so the hours I have produce the outcome I want? » The second question can be answered with evidence. The first just shuts the conversation down before any evidence arrives.
A serious executive DBA, run in hybrid format, takes on average 15 to 20 hours of personal work a week, spread across three years. That range holds steady across established executive DBA programs – Penn State Smeal, Fairfield, Houston Bauer, and others – so it is the figure to plan against.
In practice, that’s roughly ten hours of reading and analysis and another five to ten of writing – your thesis, your literature reviews, your research notes. Most of it is asynchronous, on your own schedule, with no real-time pressure beyond the milestones your supervisor sets.
In practice it tends to settle into a fixed weekly cadence – say a couple of hours reading on Monday evening, note-taking early Wednesday morning, and a longer writing block on Saturday. The exact slots matter less than having them. The candidates who finish protect the same hours every week rather than hunting for time as it appears.
To that you add three to four in-person seminars a year, usually multi-day intensives, scheduled twelve to eighteen months in advance so they can be locked into your professional calendar.
That’s the rhythm. It isn’t light work, but it is doable. Whether it stays sustainable for you depends less on these hours, which are fairly fixed, than on what surrounds them – which is the next section.
Most articles on this fixate on time management. Time management matters, but it isn’t what makes the difference. Across every cohort, three things decide the outcome, and they rank in a particular order.
This matters more than anything else, and most candidates underestimate it. If your thesis is built around a real problem from your professional context – the AI transformation in your sector, the governance challenge in a group you have helped restructure, the leadership question that defines your industry – your research stops being something you do outside your job. It becomes a deeper version of the job itself.
You’re not stepping away from your work to write a thesis; you’re investigating your own work with rigor and producing knowledge that makes you more valuable to the people who already employ you. The 15 to 20 hours a week stop feeling like a second job and start feeling like an investment that compounds.
When the question is misaligned – a generic topic picked because it sounded « doctoral enough » – the math breaks. The hours start to feel stolen, the motivation drains, and this is where most of a program’s dropouts cluster.
Three people matter here, in this order: your family, your employer, your academic supervisor.
The family conversation needs to happen openly, before you commit, not afterward as damage control. A partner, and children if you have them, didn’t sign up for three years of lopsided weekends. They should be part of the decision rather than told about it once it is made.
Your employer is rarely a blocker when the research topic lines up with a strategic question in your company. A thesis that digs into a real business problem inside your organization is an investment for them as much as for you, and the conversation tends to go better than candidates expect when it is framed that way.
Your supervisor is the one most candidates realize matters only too late. The quality of the exchange, how reachable they are between sessions, how rigorous the feedback is – all of it compounds over three years. A good supervisor can make a hard year productive; a distant one can leave you isolated in a year that should have been manageable.
« Hybrid » is a label, not a guarantee. The questions that separate a serious hybrid DBA from a marketing one are concrete. Are the in-person seminars scheduled twelve to eighteen months ahead, so they lock into an executive calendar? Is the supervisor reachable between sessions, or only at scheduled milestones? Is the cohort small enough for real peer dialogue, or is it a lecture hall in disguise?
Those are the criteria that matter – not the brochure, not the LinkedIn testimonials. The academic literature on dropout in online and distance learning puts the risk across a wide range that shifts a lot with program quality, support, and workload. Criteria like these, taken seriously, are the structural answer to that risk.
You will give some things up – not figuratively, but in a literal, calendared way, for three years.
Your weekends won’t be fully yours. Three or four of them a year will be in seminar mode, on campus, in intensive cohort work. Several more – maybe fifteen or twenty across the year – will be partial, with mornings or full Saturdays given over to writing.
Some of your social calendar gives way: the non-essential parts, the gatherings you attended out of obligation more than connection. Your reading for pleasure narrows. Your scrolling time is the first thing to go, and the one you’ll miss least.
Some of your operational responsibilities at work, the secondary ones especially, get delegated. In practice that means handing a recurring report to a deputy, or letting someone else chair the weekly review you have always run yourself. It is less a side effect than a useful push toward the delegation most experienced leaders know they have been putting off.
Some things should not give way, though. Your time with family, young children especially: the DBA doesn’t excuse you from being present, it pushes you to be more deliberate about it. Your sleep: cutting it to fit more in is the surest way to fail a doctorate, and the work will show it. Your physical health, and your core responsibilities at work. The DBA gets added to your professional life rather than replacing it. If the only way it fits is for your day job to collapse, the timing is wrong – and so is the program.
One thing worth keeping in view: Deloitte’s 2024 Workplace Wellbeing Research, a survey of 3,150 C-suite leaders, managers, and workers, found that around half of managers already report being burned out – before any doctorate is added – and the C-suite is far from immune. Layering a DBA onto an already over-extended life is a real risk. The answer isn’t to push harder; it is to settle clearly, with yourself, your family, and your program, what gives way and what doesn’t before the first seminar.
If the trade-offs still add up for you, a useful next step is to talk to someone who has guided plenty of executives through them. Speak with the program director.
The ISC Paris DBA assumes you stay professionally active across all three years, and the format is built around that as a practical matter, not a marketing line.
The program runs over three years in hybrid format. Year One is built around foundational coursework – 155 hours of training in research methodology and advanced management concepts, delivered through residential workshops in Paris combined with online sessions. Years Two and Three shift the weight toward personalized supervision and thesis work, with residential periods in Paris interspersed with online masterclasses and individual supervision.
Cohorts are kept intentionally small, which makes room for genuine peer dialogue and lets the supervisor be more than a name on a milestone calendar – reachable between sessions, not only at them.
The in-person seminars in Paris are scheduled well ahead, so they fit the calendar of someone whose meetings get locked twelve to eighteen months out. The online components are made to fit the asynchronous hours of a working life – evenings, early mornings, the rare quiet afternoon between commitments.
The program awards 180 ECTS credits over the three years, 60 of them in the first year. It follows the international standard for executive doctoral education rather than a regional certification. The exact rhythm of seminars, supervision, and online sessions is laid out on the DBA program page.
The question to ask isn’t « are you ready? » No one is ever fully ready for a doctorate, and framing it that way pressures you more than it informs you. It also isn’t « do you have the time? » The time you have is shaped by how the program is structured, not the other way around.
The real question is narrower: is there a problem, rooted in your actual professional context, that you would want to spend thirty-six months investigating with rigor – one that would make your work more valuable, not just your resume?
If the answer is yes, the rest follows. The format works, the hours fit, and the sacrifices, real as they are, buy something that compounds. The structure exists to make that yes workable.
If the answer is no, no amount of calendar engineering will save the project. A DBA is less a credential you collect than a research practice you live in, and without that question the practice never takes root.
If you’re still weighing whether the DBA is the right format – against an EMBA or a traditional PhD – that is the subject of how a DBA differs from the more familiar MBA or PhD routes. More practical questions about structure, eligibility, and admissions are answered on the DBA program FAQ.
