How to Turn Professional Knowledge Into a Book People Will Read

A lecturer has taught the same subject for twelve years. Her laptop holds lecture slides, examination questions, journal articles and a thick folder marked “Book”. She starts by arranging the slides into chapters. By page 40, the manuscript sounds like a classroom in which the teacher has stopped to explain nothing. The person who misses a point cannot raise a hand.

Professional experience can give a book authority. It does not automatically give it shape. The writer knows too much, the audience in the room has disappeared, and familiar shortcuts on a slide can become gaps on a page. A useful book has to be built for the person reading it alone.

Choose a reader, not an impressive subject

“Everything I know about leadership” is an enormous writing project and a vague buying proposition. A narrower promise might be “a guide for new supervisors managing their first team in a small Zambian organisation”. That reader has recognisable problems: giving instructions to former peers, dealing with lateness without humiliating staff, and holding a useful meeting when there is little time.

A headteacher might write for newly appointed school leaders, parents of children changing schools, or fellow educators designing reading programmes. Those are three different books. A construction professional could explain building a modest home to first-time owners, train site supervisors to check work, or tell the story of a career. Choosing one does not mean the others are unimportant. It tells you which questions the present book must answer.

Write a single working sentence before drafting: “This is for [reader] who needs to [decision or task] and currently struggles with [specific obstacle].” It may be clumsy. Its purpose is to stop attractive but irrelevant material entering the book. If a chapter does not help that reader, perhaps it belongs in another project.

Do not assume that an official title makes the audience. A retired district officer may have valuable knowledge, but a stranger will buy the book for the insight it offers, not because the author’s full career record fills two pages. Experience is the source material. The reader’s need is the organising principle.

Listen for the questions you have answered a hundred times

The beginning of a practical book is often hiding in repeated conversations. A farmer trainer keeps explaining why a good harvest can still leave someone short of cash. A nurse educator is repeatedly asked how to understand a particular form. An entrepreneur finds that new shop owners mix household expenses with business sales. Each repeated question suggests a chapter or a section, provided the writer can address it accurately and within their expertise.

Keep a question log for a few weeks. Note the questions people actually ask, the wrong assumption beneath each one and the example that finally helps them understand. Remove names and private details. Look for a sensible order: what the reader needs to understand first, what decision follows, and where they will need to check or ask for specialist help.

A book about running community projects, for instance, should not begin with a dense history of every funding model simply because the author knows it. A first-time project coordinator may first need to know how to describe the intended result, record commitments and notice early that a plan is slipping. The background matters when it helps with one of those tasks.

If you are converting academic work, that change of audience is particularly important. Our article on turning a thesis into a book looks at why a dissertation’s structure seldom serves ordinary readers unchanged.

Turn expertise into decisions on the page

Professionals often write in conclusions. “Stakeholder engagement is essential.” “Maintain proper records.” “Prioritise quality control.” These may be sound ideas, but a reader facing a real situation needs to see what they mean.

Take “maintain proper records” in a guide for a small shop. A useful section might show an owner recording opening stock, purchases, sales and money taken home, then discovering why the cash in the drawer does not match the apparent profit. The numbers, if used, can be clearly labelled as an illustration. The reader sees a mistake they might make and a way to check it.

For a site supervisor, “check materials before use” could become a sequence: confirm the agreed specification, inspect what was delivered, record a discrepancy and speak to the responsible person before the material is installed. Technical or safety instructions must be checked by a qualified practitioner and against current requirements; a book should not pretend that a general example replaces a professional site assessment. The lesson for the writer is to show a decision and its consequence, not to fill pages with commands.

Try a simple test on every major piece of advice. After the paragraph, could a reader explain what to look for, what to do next and when to seek help? If not, add the missing reasoning. The best examples need not be spectacular. A delayed invoice, a misunderstood school notice or a meeting that ends with no person assigned the work can teach more than a heroic success story.

Make the language travel beyond your office

An acronym used daily in a university, NGO or clinic may mean nothing to a new reader. Explain it when it first appears. Terms such as “capacity building”, “operationalise” and “stakeholder alignment” can sometimes be replaced by what the people actually did. Which capacity? Who changed their practice? How would the reader notice?

This does not mean removing necessary technical vocabulary. If a concept has a precise name, define it in ordinary language and then use it consistently. A book for professionals can be sophisticated without assuming everyone has attended the author’s workshops. A book for the public must be especially careful not to glide over risks and exceptions merely to sound simple.

Think of a practitioner describing a rural water project. The author knows why a maintenance committee was formed. A reader may need to know who collected the contributions, who could authorise repairs and what happened when the pump failed after the launch photographs were taken. Those specifics carry knowledge. A generic sentence saying “community ownership ensured sustainability” does not.

Local detail is useful when it clarifies the work. A case about arranging delivery between Lusaka and Mongu may show a logistics problem better than an imported example involving a warehouse network that the intended reader will never use. Do not add a Zambian place name to a generic paragraph and call it localisation. Let the setting alter the actual decision.

Protect the people behind the experience

A professional may have years of case notes, photographs, client files, student work or internal reports. Possessing those materials does not mean every detail belongs in a public book. Remove identifying information where appropriate, obtain permission when needed, and check employment agreements, professional obligations and rights in photographs or documents before using them. Sensitive fields may require specialist legal or professional advice.

Changing a person’s name alone may be inadequate if colleagues can still recognise the event from the job title, location, date and distinctive circumstances. A composite example should be labelled as illustrative rather than presented as a documented case. If a real quotation appears, verify the words and the right to publish them. Readers deserve both useful teaching and honest treatment of the people whose lives supplied it.

The same rule applies to the writer’s claims. A consultant may remember that a particular approach worked in one programme. That experience can be described carefully; it does not establish that the approach works for every school, clinic or business in Zambia. Distinguish observation, evidence, opinion and an example invented to teach a method. If guidance depends on current regulations or procedures, check authoritative sources before publishing and give readers a way to check updates.

Test one chapter before writing twelve

Choose a chapter that demonstrates the book’s real method, not only an introductory speech. Give it to two or three plausible readers who are not obliged to compliment you. Ask them what they would do differently after reading, where they got lost and what question the chapter failed to answer. If an explanation only works after you spend ten minutes talking them through it, the page needs that missing explanation.

Do not mistake every request for more detail as an instruction to add another long chapter. The reader may need one diagram, a worked example or a clearer transition. Conversely, a section that everyone skims may be background that belongs in a short note or appendix. The pilot helps you establish a useful level of detail before repeating the same weakness across the manuscript.

Once the chapter works, outline the remaining chapters as a progression of reader decisions. Then consider a suitable professional edit. An editor can spot where the specialist has skipped a step or where the book has become a transcript of a workshop. If writing the prose is difficult while the expertise is strong, ghostwriting is another arrangement to understand carefully, with clear expectations about voice, research and approvals.

Think about how the book will be used

A handbook read at a desk may benefit from checklists and room for notes. A short book sold after a training session should be useful even to someone who did not attend the session. A lecturer’s course companion may need examples that students can revisit without hearing the lecture again. The form follows the use, and those design choices affect length and printing cost. Our guide to judging a book’s length can help once the audience and material are clearer.

The author may hope the book brings training invitations, clients or institutional orders. Those are possible aims, not automatic results of publication. A useful first test is whether someone outside the author’s workplace would pay for and use the book on its own. Write the back-cover promise in plain language and see if the chapter you tested fulfils it. What should go on the back cover? explains how to make that promise visible to a stranger.

A career can supply a hundred stories. The writer’s job is to choose the ones that make a reader more capable, curious or informed. The measure of the book is not how much experience it contains. It is what the reader can understand and do with the experience that made it onto the page.

If you have spent years explaining one subject to others, which question do people keep asking that you still have not seen answered clearly in a book?