Some practice advice for doing consulting and academic oriented dissertation projects for MBA and Housing Studies students (information from perplexity.ai)
Shared foundations (both types)
- Clarify a dual aim in week 1: a problem statement for practice (what hurts whom, where) and a research aim for theory (what gap or debate you speak to). Write 2–3 sentences for each and keep revisiting them as the project evolves.
- Design for implications from the start: note possible theoretical, practical, and future‑research implications in your proposal so your later “Implications & Recommendations” chapter is grounded in your data, not speculative.
- Plan a strict 4‑month timeline: break work into weekly tasks (reading, instruments, fieldwork, analysis, writing) and pre‑book supervisor check‑ins as milestones; treat this as non‑negotiable given your part‑time status.
Mainly consulting‑oriented dissertations
Design and framing
- Define stakeholders and value early: specify which actors (e.g. housing agency, developer, NGO, resident group) and what “value” means (cost savings, service quality, tenant satisfaction, policy legitimacy), drawing on consulting and value‑co‑creation literature for your framework.
- Turn the client brief into researchable questions: convert “improve process X” into 2–3 sub‑questions (diagnostic, explanatory, and design/solution‑oriented) that you can answer with feasible methods inside 4 months.
Ensuring academic value
- Anchor the project in theory: use relevant concepts such as service‑dominant logic, value co‑creation, sensemaking, governance or implementation theory to interpret findings, not just describe the client context.
- Explicit “theoretical implications” subsection: explain how your findings refine existing models of consulting, housing policy implementation, user participation, or governance structures, even if the data come from a single case.
Ensuring practical value
- Prioritise actionable recommendations: develop a short, SMART‑style recommendations set directly tied to each key finding and to the client’s constraints (budget, politics, capacity).
- Produce two outputs: an academic dissertation and a concise client‑facing deliverable (briefing note, slide deck, executive summary) that translates theory‑laden insights into operational language and clear next steps.
Consulting vs academic emphasis
|
Dimension |
Consulting
oriented focus |
Academic
oriented focus |
|
Primary
driver |
Stakeholder
problem and decision need. |
Research
gap and theoretical puzzle. |
|
Main
contribution |
Actionable
recommendations, process change, value delivery. |
Conceptual
clarification, model testing, gap addressing. |
|
Theoretical
framing |
Lean but
targeted; borrowed to interpret the client case. |
Central
and more extensive; frames the whole design. |
|
Methods
choice |
Often mixed:
interviews, workshops, basic quant, document analysis. |
Driven
by the research question (may be more specialised). |
|
Implications
section |
Emphasises
practice, with a concise theory note. |
Emphasises
theory, with a well-argued practice note. |
|
Final
deliverables |
Dissertation
+ client report / slide deck. |
Dissertation
+ potential article/ conference abstract. |
Mainly academic‑oriented dissertations
Design and framing
- Start from a tight gap: use recent review and empirical articles to identify a precise gap (e.g. “we know little about X in Y context” or “conflicting evidence on relationship between A and B in housing market Z”).
- Align question, theory, and method: ensure that your conceptual framework, variables/constructs, and chosen methodology match the gap you claim to address, and state this alignment explicitly in your introduction.
Ensuring academic value
- Make implications for theory explicit: dedicate a clear section to how your findings support, refine, or challenge specific models, concepts, or mechanisms, not just general statements of “adding to literature”.
- Reflect on limitations and future research: use a structured discussion of limitations to motivate realistic, specific avenues for further work, which is a marker of academic maturity.
Ensuring practical value
- Translate theory into levers: for each key theoretical insight, spell out what it implies for at least one actor (policy makers, regulators, housing managers, investors, NGOs) in your context.
- Offer targeted, feasible recommendations: ground your recommendations in the empirical findings and context (e.g. Hong Kong vs Singapore housing markets) rather than generic best practice, and acknowledge trade‑offs or constraints.
Time‑bounded practice for part‑time 4‑month projects
- Front‑load design (first 3–4 weeks): finalise aims, questions, framework, methods, and access plans quickly to preserve enough time for data and writing.
- Lock a writing routine: write short sections weekly (e.g. methods, context, partial findings) instead of waiting for “after data collection”, using an outline with bullets turned gradually into prose.
- Use supervisors and peers strategically: schedule structured check‑ins with clear questions and send short pre‑reads so feedback can sharpen both academic and practical angles without derailing your timeline.
If you share your current topic ideas for MBA and Housing Studies, more tailored suggestions can be given on how to shape each into a consulting‑oriented versus academic‑oriented version within a 4‑month, part‑time window."
Core Design Principles
Literature and Methods Strategy
Analysis and Synthesis Tactics
Chapter Structure and Outputs
Hybrid Dissertation Template
|
Chapter |
Academic
Focus |
Consulting
Focus |
Hybrid
Bridge |
|
1:
Introduction |
Research
gap + objectives (e.g., gentrification theory in HK contexts) |
Client
problem statement (e.g., Sham Shui Po resident risks) |
Dual
significance + pragmatic aims |
|
2:
Literature Review |
Theory
synthesis + gaps |
Practitioner
links to concerns |
Visual framework
diagram |
|
3:
Methodology |
Philosophy
justification (pragmatism/CR) + rigor |
Feasibility
for client data |
Mixed
methods alignment |
|
4:
Findings |
Empirical
patterns vs. literature |
Descriptive
stakeholder insights |
Cross-referenced
matrices |
|
5:
Discussion |
Theoretical
implications + limitations |
Causal
analysis for client |
Triangulated
synthesis |
|
6:
Conclusions |
Future
research avenues |
SMART
recommendations + KPIs |
Executive
summary for dual audiences |
Timeline and Risk Management
Front-load dual framing (weeks 1-2: aims, ethics, framework); allocate 40% to data/methods, 30% writing, 20% analysis, 10% revisions with bi-weekly supervisor check-ins focused on balance. Mitigate risks by prioritizing one output if needed (e.g., client deck first for momentum), using tools like Google Docs for iterative drafts and AI for synthesis checks aligned to your pragmatic style. This ensures completion with verifiable academic originality and practical impact."
Pragmatism Adjustments
Critical Realism Adjustments
Philosophy Comparison Impact
|
Aspect |
Pragmatism
Emphasis |
Critical
Realism Emphasis |
|
Core
Focus |
Practical
consequences, "what works" in context |
Causal
mechanisms, stratified reality, emancipation |
|
Chapter
5 Synthesis |
Actionable
knowledge via mixed outcomes |
Retroduction
of generative structures |
|
Hybrid
Bridge |
Triangulation
for dual utility |
Laminated
ontology unifying strata |
|
Implications |
Stakeholder-specific
recommendations |
Theory
refinement + policy critique |
|
Timeline
Fit |
Faster
validation loops |
Deeper reflexivity,
risks slight delay |
Unified Timeline Tweaks
Select philosophy by week 1 to lock methods (pragmatism for speed, CR for housing depth); allocate extra 10% time to philosophy-justified reflexivity in both. Use supervisor check-ins to audit balance—pragmatism via pilot tests, CR via mechanism mapping—ensuring deliverables like client decks reflect the chosen lens without derailing your part-time pace. Hybrid "pragmatist-CR" works if blending, testing mechanisms pragmatically."
Agile Timeline Structure
- Sprint 0 (Week 1): Dual aims, ethics approval, initial framework diagram—validate with supervisor "demo."
- Sprints 1-4 (Weeks 2-9): Lit review, methods piloting, data collection in mini-cycles (e.g., 5 interviews per sprint), daily 15-min personal stand-ups logging blockers.
- Sprints 5-7 (Weeks 10-14): Analysis iterations, draft chapters, stakeholder previews for consulting feedback.
- Sprint 8 (Weeks 15-16): Final synthesis, dual outputs, retrospective on philosophy fit (pragmatism/CR).
Iterative Tools and Practices
- Conduct personal retrospectives weekly: What advanced dual value? What to pivot (e.g., drop low-yield data if resident access lags)?
- Build in feedback cadences: Bi-weekly supervisor "demos" (5-page sprint report), mid-project client preview for practicality validation.
- Hybrid deliverables per sprint: Academic (e.g., gap matrix), consulting (e.g., resident insight brief), merging via your prism lens.
Risk Mitigation Tactics
|
Risk |
Agile
Countermeasure |
Philosophy
Tie-In |
|
Scope
creep |
Fixed
sprint goals, MoSCoW prioritization (Must/Should) |
Pragmatism:
Test "what works" subsets first |
|
Data
access delays |
Parallel
mini-pilots, secondary data buffers |
CR:
Probe absences iteratively |
|
Analysis
paralysis |
Time-boxed
synthesis (2 days/sprint), triangulation |
Dual
lenses validated per cycle |
|
Burnout
(part-time) |
80/20
rule: 80% value from 20% effort, rest days |
Reflexivity
in retrospectives |
|
Balance
tilt |
KPI
dashboard: 50/50 academic/consulting progress |
Unified
theme checkpoints |
Philosophy-Specific Agility Boosts
Pragmatism accelerates via outcome-focused sprints (e.g., pilot "what works" for affordability metrics), enabling quick consulting wins like interim resident briefs. Critical realism adds depth through iterative retroduction (e.g., each sprint maps one stratum: empirical → mechanisms), with "absence hunts" in retrospectives to sharpen emancipation. Track via a 1-page "agile manifesto" upfront, committing to adaptability over rigid plans for your MBA/Housing Studies dual goals."
1. Use Causal Loop Mapping Early to Frame Complexity
Adopt causal loop diagrams (CLDs) or rich pictures in your proposal stage to map relationships among key variables and stakeholders — for example, how housing affordability policies, resident satisfaction, and gentrification dynamics interact.
This visualizes multiple feedback loops (reinforcing vs balancing effects) and reveals leverage points for both theory building and action.
In a critical realist lens, causal loops help uncover underlying generative mechanisms that create observed trends; in a pragmatic lens, they flag points of feasible intervention for the client.
Practically, CLDs can become a framework for data coding — each theme or variable coded in transcripts can be tied to a loop node to see which feedback loops your findings strengthen or weaken.
2. Apply the Viable System Model (VSM) as a Diagnostic & Design Tool
Stafford Beer’s Viable System Model is particularly useful for consulting‑academic dissertations focusing on organizational governance, community housing management, or policy coordination.
Use VSM to test whether your studied system (e.g., a housing body, municipal redevelopment unit, or NGO network) maintains the five systemic functions essential for viability — operations, coordination, control, intelligence, and policy.
In consulting mode, it diagnoses structural weaknesses (e.g., poor coordination between housing and social service units).
In academic mode, it supports theoretical insights into systemic governance or resilience frameworks.
For a 4‑month timeline, you can apply a “light” VSM version: quickly map subsystems through interviews and documents, then evaluate systemic gaps qualitatively in Chapter 5.
3. Use Double‑Loop Learning for Reflexive Dissertation Practice
Borrow Argyris & Schön’s double‑loop learning to make your dissertation reflexive and agile over its short duration.
Single‑loop learning adjusts actions when results deviate (e.g., revising your data‑collection method mid‑way).
Double‑loop learning questions the underlying assumptions (e.g., are my research questions or definitions of “stakeholder engagement” misaligned with participants’ lived realities?).
Building a short learning log or sprint retrospective table every two weeks embeds this feedback principle formally.
Theoretically, this practice strengthens methodological transparency; pragmatically, it keeps your limited‑time project adaptive and relevant."
- Some notes on the agile literature review approaches
- A collection of blog notes on using chatgpt for research purpose.