A comparative course on how countries design, regulate and reinvent their financial systems — built module by module, specifically for COIL. Each module is self-contained and country-paired, so you can take the whole course or drop a single module into a class you already teach. The University of Kentucky and Universidad Peruana de Ciencias Aplicadas teach it together today. We are looking for the next universities to join us — anywhere in the world.
Global Financial Innovation is a comparative course on how societies move money, lend it, pool risk, fund businesses and provide for old age. At UK and UPC it runs as a single shared class: mixed binational teams, the same deadlines, the same four build sprints, with each university teaching and grading its own students.
It is delivered as self-contained modules. A partner class can take the full sequence, or run a single module jointly for one week and keep the rest of its own syllabus untouched.
One course, taught simultaneously on two continents, with students in the same teams from week one.
Collaborative Online International Learning — two universities in two countries teaching one course together, online, as part of a normal term. Students are placed in mixed teams across both campuses and work together on shared assignments and deadlines.
It is not a study-abroad trip, an exchange programme or a guest lecture. Nobody travels and nobody pays a fee. Each university enrols its own students, teaches on its own calendar and awards its own grades — what is shared is the classroom, the teams and the work. For most students it is the only genuinely international project they will do during a degree, and it costs their institution nothing to offer.
Every week the class reads the same numbered module for both countries — module 05 is Payments in both, module 09 is how each provides for old age — and then discusses it with somebody who has lived inside the other answer. Half the room always knows something the other half is only reading about. That is the entire engine, and it is not something either university could build alone.
Then teams build. Four times a term they design a financial product for a real market and defend it against classmates playing the incumbent firm, the regulator and the customer who has already declined. The sprints alternate which country they anchor in, so every student spends part of the term as the local expert and part of it as the newcomer.
The whole delivery is published. Every session, every reading, every workshop document and every rubric from the Kentucky–UPC class — read it before you decide.
See the Lexington–Lima class → Talk to us →The clearest short description of the course we can give you. Every module and every build sprint serves one or more of these, and the published delivery carries an outcome map marked primary or reinforced — so if your programme needs a crosswalk, it is already written. They hold whichever modules you take.
Explain how economic, historical, and cultural factors influence the design of financial services around the world.
Compare and contrast financial products, institutions, and regulations across countries.
Identify and describe major forms of financial innovation and financial technology in banking, lending, payments, insurance, and investments.
Analyze how values and public policy choices shape financial inclusion, consumer protection, and access to credit in different countries.
Evaluate the benefits, risks, and unintended consequences of financial innovation in a global context.
Apply comparative reasoning to assess why similar financial problems are solved differently across countries.
Interpret real-world examples of global fintech firms, financial reforms, or regulatory approaches using course concepts.
Communicate clearly, in writing and discussion, about global financial systems and innovation using appropriate terminology and evidence.
Navigate the discussions and tensions around citizenship in a globalizing and interconnected society.
Evaluate how structures or institutions intersect with global trends and dynamics considering local cultural, social, political, financial, economic and other factors.
Demonstrate ethical approaches to resolving individual and collective decision-making in a globalizing and interconnected society.
A module is reading plus a build sprint, and the sprint is where the learning happens. Teams design a financial product for a real market and defend it against classmates playing the incumbent, the regulator and the customer. Each one is a country paired with a product. These are built and tested:
A dominant wallet already has most of the country. Find the customer it structurally cannot serve.
Read the case pack → 🔒 PeruIndividual retirement accounts, repeatedly opened early. Design for a saver who has seen the rules change.
🔒 Sign in to read → 🔒 United StatesCover somebody the market prices out — and answer to a carrier and a state regulator.
🔒 Sign in to read → 🔒 MaliCurrency, licence and rails all set elsewhere. Choose which dependency you accept.
🔒 Sign in to read → 🔒 MoroccoA sector serving a near-universal commitment. Attack the funding side, not the product side.
🔒 Sign in to read → 🔒 MoroccoA workshop with no collateral and no readable accounts. Three moves are available; pick one.
🔒 Sign in to read → 🔒 MoroccoThe rails work and the shopkeeper still says no. Find the party whose interest pays for him.
🔒 Sign in to read → 🔒 MoroccoNo employer, no payslip. Get two mechanisms right: how she pays, and how she claims.
🔒 Sign in to read →Peru · Payments is open to everyone — read the whole case pack without an account. The rest open with a free account, and facilitator guides are available to instructors: run of show, the lines to say out loud, failure modes, and the answer key for every direction a team can take.
Request instructor access →The workshop guide is the one document that governs all of them — the rules, the four roles, block-by-block timing, what students hand in and when, and the rubric they are marked against. Read it once and every sprint runs the same way.
🔒 Open the workshop guide →Each country track runs the same numbered modules in the same order — banking, payments, credit, insurance, capital markets, pensions, inclusion, fintech. That numbering is what makes a pairing work: module 05 is Payments everywhere, so two classes assign the same number and the comparison writes itself. Every module is a self-contained read with worked examples and a self-quiz. The whole Peru track is open — read all thirteen modules without an account. The rest open with a free account.
Your country is not on this list? Tell us where you teach and who you would like to pair with. The tracks sit on a fixed skeleton, so building one is a known job rather than an open-ended research project — and it is the part we are glad to do.
Ask for your country →A module is one country lesson, one workshop, and the guide that runs it. That is the unit — take one, take four, or take the sequence.
You assign your country’s module 05; your partner assigns theirs. Same topic, same depth, same week. Neither of you researches the other’s country.
Peru · Payments anchors in Peru. The cohort that lives there can go and ask people; the other does the research and holds the adversarial roles — then it alternates.
Same rules, same four roles, same rubric, on both campuses, from the same document. It is what lets two instructors teach one session without rehearsing it together.
One module is a week. Four make a joint unit with an escalating sequence of problems. The full set is the course. Nothing breaks if you stop at one.
Not a guest lecture, not a video exchange, not a pen-pal week bolted onto a normal course. Shared teams, shared deadlines, and a genuine disagreement to resolve with somebody whose everyday experience contradicts theirs.
You cannot see the assumptions inside the system you grew up in until somebody who grew up in a different one asks why it works that way. Every student gets that, because every student is the newcomer half the time.
Four times a term, teams design a financial product and take hard questions about price, licensing and who carries the risk. No entrepreneurship background needed — the method is taught from zero and repeated until it is theirs.
The module structure is a method, not just a syllabus. A student who has worked through two countries can pick up a third and know what to look for — a durable skill in careers that will cross more borders than ours did.
“I designed a payments product with a team in another country and presented it to people who told me why it would not work.” For many, the first genuinely international work they can describe concretely.
Every claim needs a source or an honest flag that it is a guess. “I could not find this number, and here is where I looked” scores above inventing one — a rule students carry into everything else they write.
Inclusion, consumer protection, privacy, who a system leaves out — not a bolted-on week. They turn up the moment two countries answered the same question differently.
Two universities coordinate far less than people expect. Each keeps its own calendar, its own credit hours, its own admission standards and its own grading scale. What is shared is the reading map, the four sprint weeks, and the deadlines inside them.
| Supplied | You bring |
|---|---|
| An introduction to a university already teaching it, and help agreeing a shared calendar | Approval at your end, and one workable hour of weekly overlap. |
| Country tracks for both sides of the pairing — built if they do not exist yet | Your country, and any local sources or contacts you would like the track to reflect. |
| A 31-session schedule mapped module by module and tiered into pre-class and optional | The decision about what to cut or change for your term length. |
| Eight sprint packs with facilitator guides, run-of-show and answer keys | The facilities, technology support, LMS - shared LMS may be possible. |
| Rubrics, role briefs, rotation tables and a mapped outcome set | Your own grade weights, your institution's scale, and other university specific details . |
Nothing commits you before you have seen the materials and met the person you would be teaching alongside.
Your university, country, term dates, rough cohort size, and the hours you could meet a partner. One message is enough →
We introduce you to an instructor whose calendar fits yours — starting with the Kentucky and UPC pairing, which has been through the whole cycle and knows where the friction is.
If your country is not published yet, this is where it gets written — on the same skeleton, to the same standard, openly licensed like everything else.
Only the four sprint weeks need to be simultaneous. Everything else runs independently on each campus, which is what makes mismatched calendars workable.
Your delivery goes up here beside the others, credited to you and your partner, so the next pair of universities starts from your work rather than from nothing.
Run a single build sprint with a partner class as a two-week unit inside a course you already teach. Several partnerships are easiest to begin this way.
Not sure yet? Ask for instructor access and read a facilitator guide. It is the fastest way to tell whether this is a course you want to teach.
Request access →No. It is modular. The smallest useful unit is one module — a single week run jointly with a partner class, inside a course you already teach and otherwise keep exactly as it is. Add more later if it worked.
Ready. Take a module and its workshop as published and it works — that is why the facilitator guides exist. But tell us what you need changed and we will build it with you: a case reset in a market your students know, a sprint compressed into one session, readings re-cut for a different level. No charge.
No, and it is designed not to. No system is the standard the others are measured against. Every one is presented as serious answers built under real constraints, and the question is always why this answer here.
Yes, and we would like you to. The eleven published tracks are where we have reached, not a boundary. Tell us your country and your partner's and we build both, on the same thirteen-module skeleton, to the same standard.
No — that is the part we most want to help with. Tell us your term dates, cohort size and workable hours and we look for a match. If nothing fits your term yet we will say so rather than leave you waiting.
Kentucky's and UPC's do not either. Only the four sprint weeks need to be simultaneous — eight or nine shared sessions in total. The reading runs independently on each campus at whatever pace suits your term.
They do not. Deliverables and deadlines are shared; each university grades its own students on its own scale, which matters where scales differ — as between a US letter grade and a Peruvian 0–20.
You need one workable hour of overlap for the sprint sessions. Everything a student submits is individual and posted to a shared folder, so no one's mark depends on a teammate being awake — a design decision made specifically for this.
The materials are in English today. The Kentucky–UPC pairing lets teams work in Spanish inside their own breakout and translate only the sentence they report — a device that transfers to any pairing. Translations are welcome under the licence and we would like to host them.
Business undergraduates, upper-division. No prerequisite beyond an introductory finance or economics course. The sprints assume no prior entrepreneurship exposure — they teach the method from zero and repeat it four times.
The binding constraint is the pitch round: four teams fit a session comfortably, which is about 16–25 students per section on each side. Larger cohorts use parallel pitch rooms, and the facilitator guides explain how.
The facilitator guides exist for exactly that: run of show block by block, the lines to say out loud, the failure modes with fixes, a model answer for every direction a team can take, and contingencies for when the room is not the room you planned for.
Nothing, in any currency. Content is CC BY 4.0 — adapt it, re-cut it, translate it, use it commercially, with attribution. Students need a free account to read the modules. There is nothing to procure at either university.
Yes. A single build sprint runs as a two-week unit between two classes that are otherwise doing their own thing. It is a low-risk way to find out whether the partnership works before either of you rebuilds a syllabus.
Case packs, schedules and rubrics are open to any member. The facilitator guides are instructor-only because they carry the answer keys. Tell us you are teaching and we will flag your account — no charge, no ordeal.
Because every university is teaching the same modules, every one of them can pair with every other. Three partners make three pairings; six make fifteen. Each new university multiplies what is available to everyone already teaching it — which is why we would rather recruit you than simply hand you a folder.
Where this is going: every university paired with several others, not just one. Each dot has four partners.
A pairing works between any two countries. Eleven country tracks are published today — Peru, the United States, Kenya, Mali, India, China, Morocco, France, Spain, Türkiye and Brazil — and that is where we have reached, not where this stops. More are in build, and which ones get built is decided by which universities come forward.
So if you teach somewhere that is not on that list, you are not on the wrong page. Tell us your country and your partner's, and we build the tracks the pairing needs — on the same thirteen-module skeleton, to the same standard, published openly like everything else. It is a known and bounded piece of work, and it is the part we are glad to do.
Students in Lexington and Lima are in the same teams this term, working through how two countries decided to move money, lend it and provide for old age. We would like students in your country in that conversation — and the curriculum, the sprints, the rubrics and the guides are all built, published and already tested on real students. Tell us where you teach, and we will take it from there.