Forty interviews. Somewhere over 300,000 words of transcript. A coding frame that started with eight categories and now has ninety. A supervisor who asked what your findings are, and an answer that took four minutes and did not land. The findings chapter is due in three weeks and you cannot write the first sentence.
This is not a discipline problem or a data problem. It is a structural one, and it has a specific cause: coded data is organised by category, and a chapter has to be organised by argument. Nothing in the coding process converts one into the other. That conversion is a separate piece of intellectual work, and almost nobody is taught to do it.
Turn your transcripts into a findings chapter with Tesify
What it costs to stay stuck here
Postgraduate management researchers lose more time at this point than at any other stage, and the losses compound in ways that are worth naming plainly.
The obvious cost is calendar. A findings chapter that should take six weeks takes five months, and on a one-year masters that is the difference between submitting and applying for an extension. On a funded doctoral project it eats into the write-up period you were relying on for the discussion chapter.
The less obvious cost is analytical. A findings chapter written under time pressure defaults to the safest available structure — one section per theme, each opening “Participants reported that…” followed by two quotations and a paragraph of paraphrase. That chapter passes, usually. But it is also the chapter that produces the worst discussion chapter, because there is no argument in it for the discussion to develop. Examiners describe this as descriptive rather than analytical, and it is the single most common criticism of qualitative management dissertations.
The third cost is that the work never becomes a paper. A theme-by-theme description has no thesis, and journals in management reject on exactly that basis.
Why interview data resists becoming a chapter
Three specific mechanisms, all fixable once you can see them.
Codes multiply and never resolve. Coding is a divergent process — every pass generates distinctions. Nothing in the method forces convergence, so a frame grows until it has more categories than the chapter can carry. Ninety codes is not analysis; it is deferred analysis.
Themes are nouns, and arguments are claims. “Trust”, “middle management resistance” and “communication breakdown” are topic labels. They can be listed but not argued. A chapter needs statements that could be wrong: trust in senior leadership was rebuilt through operational reliability rather than through communication, and middle managers were the mechanism. That sentence has a shape. A noun does not.
The quotations start driving. Everyone has three or four transcripts where a participant said something unusually articulate. Those quotations begin to organise the chapter around themselves, and the analysis quietly becomes an anthology of your best interviews rather than an account of all forty.
The four moves that produce a findings chapter
Move 1: Collapse the coding frame to between four and seven themes
Do this before writing anything. Take the ninety codes and group them by what they are evidence of, not by what they are about. Codes about email volume, meeting frequency and reporting lines may all be evidence of the same underlying finding about information asymmetry between head office and sites.
Anything that cannot be grouped either belongs in a different chapter or is not a finding. Four to seven themes is the range a chapter can develop properly; ten becomes a list.
Move 2: Write each theme as a claim, in one sentence
For each surviving theme, write a single declarative sentence stating what you found — not what the topic was. Test each one against two questions: could a reasonable person disagree with it, and does your data actually support it across the sample rather than in three interviews?
These sentences become your section headings, or at minimum the opening line of each section. Most researchers find that two of their themes fail this test and merge into a stronger third. That is the process working.
Move 3: Sequence the claims into an argument
Themes are not independent. Order them so that each prepares the next — condition first, then mechanism, then consequence, then the exception that qualifies it. Write a single paragraph at the top of the chapter that states all four claims in order. If that paragraph reads as a coherent account, your chapter has a spine. If it reads as a list, the sequencing is not done yet.
This paragraph is also the answer to the question your supervisor asked, and the answer you will need in a viva.
Move 4: Build each section on evidence, not illustration
Within each section, follow the same shape: state the claim, establish its distribution across the sample, present evidence, interpret it, and mark the boundary.
Distribution matters more in management research than students expect. “Fourteen of the twenty operational managers described this, while none of the six head-office participants did” is a finding with structure. “Participants reported…” conceals whether you mean three people or thirty-eight. You are not counting to make the work quantitative; you are being precise about your own evidence, and examiners read that as confidence.
Quotations should be doing evidential work rather than decorating a point you have already made in your own words. Two well-chosen extracts beat six. And every section needs its boundary stated — the participants for whom this did not hold, and what that tells you.
Keeping findings and discussion separate
In management dissertations the two chapters bleed into each other constantly, and the fix is a clean division of labour. The findings chapter reports what is in your data, using your participants’ terms and your own analytic categories. The discussion chapter puts that into conversation with the literature, and that is where theory names appear.
If you find yourself citing Weber in the findings chapter, you have started the discussion early — and you will then have nothing left to say in the chapter that is supposed to make the contribution. The structure that chapter needs is set out in the seven-move guide to writing a discussion chapter. The relationship also runs backwards: your findings should answer questions your literature review chapter actually raised, and if they do not, one of the two chapters needs revisiting.
Where the tooling actually helps
Analysis software does the part it is good at and no more. Coding, retrieval and querying across forty transcripts is genuinely faster in a dedicated tool, and the options — including a free one — are compared in the review of NVivo, ATLAS.ti and Taguette. What none of them does is tell you which four claims your chapter is making. Researchers who expect the software to produce themes end up with a tidier version of the same ninety-code problem.
The same applies upstream. Transcription tools save real hours, but what your ethics approval permits is the binding constraint, as set out in the comparison of research transcription tools.
How Tesify handles the part that is actually hard
The gap is between having coded data and having a chapter, and it is a writing problem with an analytical core. Tesify is built for that gap.
You bring your themes and your evidence into a workspace where the drafting and the sources sit together, so a claim in your chapter stays attached to the material it rests on rather than to your memory of it. You can work a theme into a claim sentence, test how it reads in sequence with the others, and see immediately where a section has interpretation but no evidence behind it. Structural feedback tells you when a section is describing rather than arguing — the criticism examiners make most often, and the one that is hardest to see in your own draft.
What it will not do is decide what you found. That judgement is the contribution, it has to be yours, and any tool that offers to make it for you is offering you something an examiner will take apart in a viva. Tesify is built to keep the reasoning in your hands and take the friction out of everything around it.
There is a free tier, so you can put a single chapter through it before deciding whether it earns a place in your workflow.
Start your findings chapter with Tesify
Frequently asked questions
Is using an AI tool to write a findings chapter allowed?
Policies differ by institution and you must check your own before using any tool. The line most UK universities draw is between support for your writing and substitution for your thinking. Structuring, drafting assistance and feedback are generally permitted where declared; presenting generated analysis as your own findings is not.
Will an examiner be able to tell?
An examiner will establish in a viva whether the analytical judgements are yours by asking why you grouped codes as you did and what you rejected. A chapter whose reasoning you cannot reconstruct out loud fails that test regardless of how it was produced, which is why the analysis has to remain your own work.
Is my unpublished interview data safe in an AI tool?
This is the right question to ask before uploading anything, particularly where participants consented under specific conditions or an organisation granted access commercially. The legal position and the five questions to put to any tool’s terms are set out in our article on putting unpublished thesis data into AI tools.
How much does Tesify cost?
There is a free tier that lets you work through a chapter before committing, with paid plans for sustained use across a full dissertation. Current pricing is on the Tesify site; check it at source rather than relying on figures quoted elsewhere.
How many themes should a findings chapter have?
Four to seven is the range most chapters can develop with adequate evidence and interpretation. Beyond that, sections become too short to argue anything and the chapter reads as a list. If you have ten, at least three are usually sub-themes of others.
Should you count how many participants mentioned each theme?
Report distribution without turning it into pseudo-quantification. Saying that a view was held by operational managers but not head-office participants is analytically useful. Presenting percentages from a purposive sample of forty implies a generalisability the design does not support.
How long should a qualitative findings chapter be?
Your programme’s word limit governs, and it varies widely. As a working proportion, the findings chapter is often the longest single chapter in a qualitative dissertation because quotations consume words. Check whether your regulations count extracts within the limit.
What if your data does not answer your research question?
This is common and usually recoverable by revising the question to match what the data addresses, in consultation with your supervisor. A dissertation that honestly reports what it found against a revised question is examined far better than one that forces unwilling data toward the original one.