<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Competition on Jack Gregory</title>
    <link>/categories/competition/</link>
    <description>Recent content in Competition on Jack Gregory</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Jack Gregory</copyright>
    <lastBuildDate>Mon, 01 May 2023 00:00:00 +0000</lastBuildDate><atom:link href="/categories/competition/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building a fragility index using factor analysis</title>
      <link>/blog/itc-fragility-index/</link>
      <pubDate>Mon, 01 May 2023 00:00:00 +0000</pubDate>
      
      <guid>/blog/itc-fragility-index/</guid>
      <description>TL;DRThe ITC Fragility Index turns a set of business-survey questions about insecurity, trust, and economic performance into a single 0–100 fragility score for each business. We use exploratory factor analysis (EFA) to uncover three underlying dimensions—Human Security, Social Cohesion, and Economic Performance—and then use confirmatory factor analysis (CFA) to test the resulting structure. The three pillars are standardized and combined to produce the final index. Along the way, we demonstrate a practical, reproducible approach to using factor analysis in R to turn a multidimensional survey into a theoretically grounded composite index.</description>
    </item>
    
    <item>
      <title>ITC Fragility Index</title>
      <link>/project/itc-fragility-index/</link>
      <pubDate>Mon, 01 May 2023 00:00:00 +0000</pubDate>
      
      <guid>/project/itc-fragility-index/</guid>
      <description>ObjectiveTo build a business-specific “fragility index” based on the International Trade Centre (ITC) Business Fragility Survey.1
DescriptionThe Business Fragility Survey is a national business-level questionnaire aimed at assessing how small and medium enterprises (SME) cope within fragile social and political environments. The Survey contacted around 2,600 businesses from eight developing countries, of which over 1,100 provided complete responses. The Survey was carried out in partnership with domestic business support organizations.</description>
    </item>
    
    <item>
      <title>Creating a proxy for local instability using geospatial event data</title>
      <link>/blog/itc-instability-indicators/</link>
      <pubDate>Tue, 21 Mar 2023 00:00:00 +0000</pubDate>
      
      <guid>/blog/itc-instability-indicators/</guid>
      <description>TL;DRThis blog shows how to use Armed Conflict Location and Event Data (ACLED) event data and geospatial techniques in R to construct location-specific indicators of local instability. Using hypothetical business locations in Ecuador, I demonstrate how nearby adverse events can be aggregated into a simple measure of exposure to insecurity, which can then be used to compare locations or incorporated into analyses of business outcomes.
IntroductionIn the Western world, we can sometimes overlook the benefits derived from operating within stable and peaceful communities.</description>
    </item>
    
    <item>
      <title>ITC Instability Indicators</title>
      <link>/project/itc-instability-indicators/</link>
      <pubDate>Tue, 21 Mar 2023 00:00:00 +0000</pubDate>
      
      <guid>/project/itc-instability-indicators/</guid>
      <description>ObjectiveTo build business-specific “instability indicators” based on the International Trade Centre (ITC) Business Fragility Survey and Armed Conflict Location and Event Data (ACLED).1
DescriptionThe Business Fragility Survey is a national business-level questionnaire aimed at assessing how small and medium enterprises (SME) cope within fragile social and political environments. The Survey contacted around 2,600 businesses from eight developing countries, of which over 1,100 provided complete responses. The Survey was carried out in partnership with domestic business support organizations.</description>
    </item>
    
  </channel>
</rss>
