AI Processed Human Approved
How can practitioner researchers overcome the divide between academia and industry to create real-world impact?
Key findings
- IS practitioner doctorates facilitate knowledge exchange through boundary-spanning activities including research design adaptation, multi-channel dissemination, and creating symbolic discourse.
- Practical impact progresses through proof-of-concept, proof-of-value, and proof-of-use stages, each requiring different combinations of social, cultural, economic, and symbolic capital.
- Environmental forces such as academic vs. practice doxa (institutional norms) and habitus (professional dispositions) create positional conflicts that require active negotiation and tailored incentives to sustain engagement.
What it means for you
- CIO / IT Executive: On Monday morning, schedule a 30-minute meeting with your direct reports to initiate a 'practice impact review' focused on one ongoing IS project. Ask each person to identify one specific academic insight or research finding from a recent external study or internal research initiative that could be directly applied to improve that project's current proof-of-concept or proof-of-value stage, and assign them to explore this application by end of week.
- IT Manager: On Monday morning, identify one specific, recent academic paper or conference proceeding relevant to a current team challenge. Forward this paper to your team with a concise note asking for a brief, 1-2 sentence summary of its most practical takeaway and how it *might* apply to your current proof-of-value stage objective by Tuesday afternoon.
- Business Strategist: On Monday morning, review the key performance indicators (KPIs) of one strategic business initiative currently underway. Identify which KPIs are not meeting expectations and, using the 'proof-of-value' framework, draft a one-page hypothesis on how a novel IS application or process, potentially informed by academic research, could demonstrably improve these specific KPIs within the next quarter.
- Researcher: On Monday morning, select one recent academic publication where you are the lead author and identify its 'proof-of-use' stage potential. Draft a single-slide executive summary that articulates the core problem addressed, the practical solution proposed, and one tangible benefit for a specific industry practitioner role (e.g., IT manager, business analyst), and share it with three relevant practitioner contacts for feedback by Wednesday.
- Policymaker: On Monday morning, review the current grant application criteria for technology innovation funding. Identify if and how 'demonstrable practical impact' is explicitly assessed, and draft a brief proposal to incorporate a specific requirement for applicants to detail their strategy for achieving 'proof-of-value' or 'proof-of-use' within a defined timeframe, alongside theoretical contributions.