extended-abstract¶
draftingprivate (curator-owned)paper-draftingCurator-private skill — copy text from 100xOS/shared/skills/writing/extended-abstract.md.
Workshop Extended Abstract Blueprint¶
This skill defines the structure and argumentation pattern for workshop extended abstracts (3–8 pages), as derived from actual accepted submissions to WISE and the Workshop on Digital Markets.
An extended abstract is not a long version of a journal abstract. It is a compressed version of a full paper: it presents the research question, theoretical framework, method, preliminary results, and contribution — all in a form that demonstrates the work is viable and worth discussing at a workshop.
Section Structure¶
Use the following section headings and flow. This is the actual structure that has been accepted at top IS workshops.
1. Introduction (~1–1.5 pages)¶
Open with a concrete, grounded description of the phenomenon — anchored in real-world facts, market sizes, regulatory developments, or observable trends. Not generic claims about "digital transformation" or "emerging technologies."
Pattern: 1. Phenomenon (2–3 sentences): What is happening in the world? Ground it with specifics. 2. Novel aspect (2–3 sentences): What new behavior, strategy, or mechanism has emerged? Why is it non-obvious or counterintuitive? 3. Gap (1–2 sentences): What does the literature not yet explain about this? 4. This paper (2–3 sentences): "This study aims to..." or "This paper conceptualizes how..." — state the research objective, the approach (conceptual framework, analytical model, empirical analysis), and the setting. 5. Prior work positioning (1–2 sentences): Briefly note what few existing studies have done and how this work goes beyond them. 6. Preview of approach (2–3 sentences): "We begin by developing... Then, we put our framework to empirical scrutiny by analyzing..."
Example opening sentence: "Creators of the creator economy have been continually seeking new strategies to monetize their creations in recent years."
Example pivot to contribution: "This paper conceptualizes how smart durable goods producers may leverage resale fees to shift value capture from platforms back to producers — a process we term 'de-platformization.'"
2. Conceptual Framework / Model (~1.5–2.5 pages)¶
This is the theoretical core. Present either: - A conceptual framework with hypothesis development (empirical papers), or - An analytical model with formal propositions (theory papers), or - Both.
For conceptual framework + hypotheses: 1. Define the key constructs and mechanisms in plain language. 2. Introduce a stylized model if applicable (notation: $C_{i,t}$, utility functions, profit functions). 3. Derive each hypothesis from the logic of the framework. State hypotheses as standalone labeled blocks (e.g., "Hypothesis 1: A rewarding strategy induces backward spillovers in the secondary market."). 4. Use figures to illustrate mechanisms (e.g., "Figure 1 illustrates this phenomenon, where the reward enhances the perceived value...").
For analytical model + propositions: 1. State assumptions explicitly and number them. 2. Define the game structure (players, timing, information). 3. Present profit/utility functions with full notation. 4. State propositions formally, then explain the intuition in prose. 5. Include a "Key Theoretical Results" subsection summarizing main findings.
Key guideline: The model/framework section must make the contribution intellectually clear even without the empirical results. A reader should understand why the hypothesized effects occur, not just that they are hypothesized.
3. Empirical Setting / Research Design (~0.5–1 page)¶
Describe the empirical context, data, and method concisely.
Pattern: 1. Setting (2–3 sentences): What real-world case or dataset? Why is it suitable? 2. Data (2–3 sentences): Source, time period, key variables, sample size. Include concrete numbers: "over 1.3 million customers and 22.7 million transactions." 3. Method (2–3 sentences): Identification strategy (DiD, IV, VAR, etc.), treatment and control groups, key specifications. 4. Validity (1–2 sentences): Brief note on parallel trends, robustness, or identification assumptions.
Example: "Our research design leverages the quasi-natural experiment of Yuga Labs' rewarding strategy... We obtained data for all transactions from Flipside Crypto."
4. Preliminary Empirical Results (~0.5–1 page)¶
Present initial findings. "Preliminary" is acceptable — workshops expect work-in-progress.
Pattern: 1. Lead with the direction and magnitude of the main result. 2. Reference the table/figure: "Table 1 presents the results of the difference-in-difference analysis." 3. Interpret coefficients in substantive terms: "corresponding to an increase of approximately 74%." 4. Note robustness if available: "To ensure robustness, we also examine the rewarding strategy of another creator..." 5. Be honest about what is not yet done: "In the next stage of our research, we will incorporate primary market data to analyze..."
5. Conclusion and Discussion (~0.5–1 page)¶
Wrap up with contributions, implications, limitations, and next steps.
Pattern: 1. Summary (2–3 sentences): Restate what was done and what was found. 2. Implications (2–4 sentences): What does this mean for theory and practice? Be specific. 3. Generalizability (1–2 sentences): How do findings extend beyond the specific setting? 4. Next steps (1–2 sentences): What will be done before the full paper? "In the next stage, we will..." 5. Broader relevance (1–2 sentences, optional): Connect to wider trends or policy.
6. References¶
Standard bibliography. Use author-year style (natbib/plainnat). Keep it tight — only cite what is used in the text.
Argumentation Flow Across Sections¶
The argument builds as a chain:
- Introduction: "X is happening → Y is the novel/puzzling aspect → literature hasn't explained Y → we provide a framework and empirical evidence"
- Framework/Model: "Here is the mechanism that explains Y → it predicts these specific effects (H1, H2...)"
- Empirical Setting: "Here is a real case where we can test these predictions"
- Results: "The data support / partially support our predictions — here are the magnitudes"
- Conclusion: "Therefore, Y works as our framework predicts → this matters because..."
Each section's opening sentence connects to the previous section's conclusion. The reader should never wonder "why am I reading this section?"
Length and Formatting¶
- Total length: 3–8 pages depending on the workshop's call for papers. Check the CFP.
- Figures and tables count toward the page limit. Use them selectively — 1–2 figures for the framework, 1 results table.
- Double spacing is common for workshop submissions. Check the CFP.
- No appendix. Everything must fit in the main body.
What NOT to Do¶
- Do NOT use the "Motivation / Expected Contribution / Feedback from Workshop" structure. This is a generic template that signals the work is not yet developed. Use the section structure above.
- Do NOT write the introduction as a literature review. The introduction motivates the research question. Literature is woven in to support the argument, not surveyed comprehensively.
- Do NOT present the model without intuition. Every formal result needs a 1–2 sentence plain-language explanation of why it holds.
- Do NOT hide the absence of results. If results are preliminary, say so directly. If a hypothesis is not yet tested, state what you plan to do. Workshop reviewers value honesty about the stage of the work.
- Do NOT write a teaser. The extended abstract must contain actual substance — the framework, the model, preliminary evidence. "We plan to investigate..." without a framework is a research proposal, not an extended abstract.
- Do NOT use vague contribution statements. Not "we contribute to the literature on X." Instead: "We are the first to derive [specific thing] for [specific context], allowing [specific new analysis]."
- Do NOT include an abstract section at the top. An extended abstract is the abstract. Jump straight into the Introduction. (Exception: some CFPs require a short 150-word abstract before the extended abstract — if so, follow the separate abstract skill.)