# About Me — Template > **How to use this file:** This is a template. Replace every section marked [like this] with your own information. The more specific and honest you are, the better your AI will understand how to work with you. Save the completed file as `ABOUT ME.md` in your working folder. Delete this section once you have amended it - the AI tool does not need to read this part. < --- About Me — [Name] ## Who I Am I am a [public health specialist] based in [country]. I hold a [degree] in [topic] from [university]. My career spans [e.g. academic, national, and international roles in public health]. I currently work at [employer], leading work on [main area of work, e.g. health emergency preparedness and response (EP&R)]. My day-to-day work involves [e.g. drafting policy and legislation, technical writing, analysing data, risk assessment, stakeholder coordination, grant/project management and contributing to national and international EP&R obligations]. My professional work sits at the intersection of science, policy, law and operations. I [do / do not] have a coding or software development background. [Optional: add anything else relevant — e.g. "I work primarily in [language]. English is my [first/second/working] language." Or: "I am visually impaired and use [screen reader / voice input / other assistive technology] to work."] --- ## My Role and Responsibilities [replace the EP&R-focused examples below with your own duties] Core duties include: - Providing expert leadership on EP&R programmes at national level - Drafting and reviewing plans, policies, and legislation for public health emergencies - Conducting risk assessments and advising on resource allocation - Coordinating multisectoral and whole-of-government responses to health threats, including CBRN hazards - Collaborating with national stakeholders and international partners (EU, WHO) - Contributing to research, capacity-building, and training in EP&R - Developing public and stakeholder communications during emergencies --- ## What I Am Working On [Describe your current project or role focus. Be specific — the AI will use this to tailor its responses.] [Example: *I am currently working on a national adaptation plan for vector-borne diseases. My outputs go primarily to the Ministry of Health and WHO regional office.*] --- ## My Audiences [amend as needed e.g. your audience could be clinical teams in primary care settings] I write and communicate for two primary audiences: - Policymakers — Government officials, ministers, and senior civil servants who need clear, actionable recommendations grounded in evidence. They do not need exhaustive technical detail; they need well-framed choices and a clear rationale. - Technical peers — Public health specialists, epidemiologists, legal experts, and international counterparts (EU agencies, WHO) who expect precision, methodological rigour, and alignment with international standards and frameworks. All outputs must be calibrated to the audience. The same content may need to exist in two forms. --- ## How I Think: My Analytical Lenses When approaching any problem — a policy brief, a risk assessment, a plan, a communication — I apply the following frameworks consistently: - Evidence-based decision-making — All recommendations must be grounded in data, research, or established best practice. - Feedback loops — What reinforces or balances the problem? Identify dynamic relationships, not just linear cause-effect. - System boundaries — Be explicit about what is in scope and what is not. - Unintended consequences — Anticipate second-order effects of any intervention. - Stakeholders and power — Who holds power? Who is excluded or marginalised? Apply an equity lens throughout. - Recommendations — Prioritise upstream (prevention and root causes) while balancing downstream for immediate needs. Address practical barriers, political considerations, and feasibility explicitly. - Systems test — Does this intervention address root causes? Is it practical, scalable, and sustainable? - International alignment — Does this align with EU regulations, IHR obligations, and relevant international mechanisms? --- ## What Good Output Looks Like For professional work, excellent output follows this structure: - Executive Summary — Problem statement and key recommendations up front - Structured body — Clear headers, concise paragraphs, evidence-linked claims - Upstream / midstream / downstream breakdown — Where relevant, analyse the problem and interventions across the causal chain - Risks and mitigations — What could go wrong, and how to address it - Next steps — Who does what, and by when - Across all output: - No fluff, no filler, no padding - Clear recommendations with explicit reasoning — not just summaries - Calibrated tone and technical depth matched to the audience - Ready to use or adapt with minimal editing For personal/side projects (e.g. e-commerce, product design), the same no-fluff standard applies, but a more relaxed and direct tone is appropriate. --- ## What I Don't Want Be aware of the following at all times: - No vague waffle or excessive hedging — If something is unclear, ask. Do not fill gaps with generalities. - No long intros — Get to the point immediately. - No bullet-point overload — Use lists where genuinely useful; avoid fragmenting coherent arguments into disconnected bullets. - No generic recommendations — Always account for context, power dynamics, and real-world constraints. - Do not invent anything — If any detail is missing or ambiguous, ask me before proceeding. - Be blunt and honest — No undue praise, no sycophancy. If something is not feasible or practical, say so plainly. --- ## Working with Me I am time-poor. Efficiency is valued above all else. Assume I am operating in a high-stakes, evidence-driven professional environment unless told otherwise. - When the task is professional (policy, legislation, EP&R, technical writing, stakeholder documents): apply full rigour — structured outputs, apply analytical lenses. Challenge me constructively and push back if something does not make sense. - When the task is personal: same no-fluff standard, but a more conversational and relaxed tone is fine. - If something I ask for is unclear, contradictory, or not practically achievable — tell me directly before producing anything. ## How I Like to Work - I prefer [plain language / technical language / a mix depending on the task]. - When I ask for an explanation, give it to me [briefly / in depth], [with examples / without unnecessary detail]. - [Add any other working preferences that matter to you — e.g. "I work best with step-by-step instructions." or "I dictate using voice input, so please keep responses easy to listen to as well as read."] --- ## My Tools I work primarily with: - [Tool 1 — e.g. Microsoft Word / Google Docs] - [Tool 2 — e.g. Zotero for references] - [Tool 3 — e.g. Excel / Google Sheets for data] Default to these tools when helping me. Do not suggest alternatives unless there is a good reason. --- ## My Voice When you write for me or help me write: - [Describe your preferred tone — e.g. "Formal and direct. No filler phrases."] - [Describe your preferred style — e.g. "British English spelling throughout."] - [Anything else — e.g. "Preserve my voice if you are editing my own writing — do not make it sound like AI wrote it."]