Sustaining Doctoral Momentum: A Time Architecture for the UK Executive-Researcher

Doctoral study is sometimes described as a marathon, but the metaphor misleads the UK executive. A marathon has a route, a start time and a finite demand on attention. A DBA is better understood as a long-term research practice that must coexist with board papers, travel, regulatory change and the ordinary unpredictability of senior working life. The central design question is therefore not how to find spare time but how to build a repeatable research rhythm inside a diary that was never designed for continuity. The 90-minute rule is a useful organising principle, not a rigid law.

The diary is the first research instrument

Most executive calendars are organised around responsiveness. Meetings expand, travel absorbs the edges of the day and urgent matters displace important ones. A DBA requires something different: cumulative attention to a defined problem, sustained over months and years. Without a deliberate architecture, research becomes the activity that happens after everything else has been deferred. The result is not simply slow progress; it is fragmented thinking. Reading is disconnected from writing, data collection is disconnected from analysis, and supervision becomes a sequence of updates rather than a genuine intellectual exchange.

Weekend batching is the most common response to this pressure. It is not inherently wrong. A full Saturday can be useful for a literature review or a period of concentrated writing. The danger arises when batching becomes the entire model. Weekend sprints tend to be separated by long gaps, which means the researcher must spend much of each session reconstructing the thread of the argument. Fatigue also reduces the quality of judgement. A DBA completed in exhausted weekends may satisfy a word count, but it is unlikely to produce the kind of disciplined inquiry that justifies doctoral study.

The 90-minute rule as a minimum viable unit

Ninety minutes is long enough to enter a complex problem and short enough to protect within a demanding week. It is not a guarantee of deep work, but it is a realistic threshold. Two or three protected 90-minute blocks each week will usually produce more durable progress than an occasional full day, because the rhythm maintains continuity between sessions.

Each block should have an entry point and an exit point. The entry point is a specific question: which section is being drafted, which dataset is being examined, which argument is being tested. The exit point is a short written note recording what changed, what remains unresolved and what the next block must address. This note is not administrative clutter. It is the mechanism that allows the next session to begin without a long warm-up. During the block, email and messaging should be closed. A 90-minute meeting can be moved; a 90-minute research block should be defended with equal seriousness.

A three-tier week

A sustainable rhythm has three tiers. The first is the deep-work block, ideally scheduled at a time when the executive is least likely to be interrupted. For some, that is an early morning before the diary opens; for others, it is a meeting-free afternoon or a train journey that is treated as protected time. The second is supervisory cadence. A 45 to 60 minute supervision every three to four weeks, supported by a written pre-read, is usually more productive than an unstructured monthly call. The pre-read should identify progress, problems and the specific decisions or feedback required. Supervisors can then engage with the research rather than spend the session reconstructing it.

The third tier is integration. A weekly 20 to 30 minute review should connect the research blocks to the wider programme: milestones, ethics approvals, data access, reading and writing targets. A monthly half-day can be used for synthesis, when separate notes and drafts are drawn together. A termly planning session should look further ahead, aligning the research calendar with known pressures such as board cycles, audit periods, annual leave and peak travel. This is time architecture, not time management. It recognises that the executive diary has seasons and that research must be designed around them.

Negotiating research time with the employer

Employer support is often treated as a private arrangement, but it should be made explicit. The strongest case is not that the executive needs time away from work. It is that doctoral research can contribute to the organisation through applied inquiry, better evidence appraisal and a more reflective approach to strategy. The negotiation should therefore focus on outputs and safeguards: the research question, confidentiality boundaries, data protection arrangements and the points at which findings may be shared.

A written development agreement is preferable to an informal understanding. It might specify one half-day per fortnight, a small number of study days, or the treatment of travel time on longer journeys. Line managers and HR should be involved where appropriate, not to bureaucratise the arrangement but to protect it. The conversation is stronger when framed as a professional development plan with defined commitments on both sides. Research time should not depend on the goodwill of a particular manager or the relative quietness of a particular quarter.

Warning signs of ineffective batching

Several signals suggest that the rhythm has broken down. The first is research debt: a growing pile of reading, notes and data that is never processed. The second is rescue writing, where every research session is devoted to meeting an imminent deadline rather than advancing an argument. The third is supervisory drift, in which the supervisor becomes a project manager chasing drafts rather than a critical reader. A fourth is the absence of writing between blocks. Reading without writing creates an illusion of progress but leaves the thesis undeveloped.

Batching is a tactic, not a timetable. It can be useful for discrete tasks, but it cannot carry a doctoral programme on its own. If most research sessions begin with a period of reconstruction and end with exhaustion, the model is failing. The remedy is not more intensity but a more realistic pattern of protected blocks, scheduled supervision and regular review.

A sustainable pattern

A 12-week pattern might combine two or three 90-minute deep-work blocks each week, one supervision or written feedback cycle every three to four weeks, and a monthly synthesis session. The pattern should be reviewed at the end of each term. Some weeks will fail. Travel will intervene, board papers will arrive late and family commitments will take priority. The purpose of the architecture is to make recovery possible without abandoning the programme. A missed block is a scheduling event; a missed month is a design problem.

For the UK executive, the DBA is not a test of endurance. It is a test of design. The 90-minute rule works because it respects the reality of the diary while refusing to let the diary define the limits of the research. Protected time, a disciplined supervisory cadence and an honest conversation with the employer are not peripheral supports. They are the infrastructure of doctoral inquiry.