agile# How to Use the Frugal Prototyping Method to Manage External Compliance Requirements in Education Platform (1/34)
An education platform SME running SAFe with a small team of two to five people has an external compliance problem. The company runs a learning management platform serving K-12 school districts and offers professional development courses for teachers. It has been around for seven years with sixty two employees. The product development organization for the new student data analytics module has four people running SAFe. (2/34)
The external compliance requirements are overwhelming. The team spends thirty five percent of its time on compliance documentation instead of building product. That means the team falls behind on the product roadmap. Falling behind means missed feature delivery dates. Missed dates mean lost school district contracts. Last quarter, those lost contracts cost the company fifty three thousand dollars (3/34)
. That was thirty one percent of the quarterly revenue from the student data analytics module.
The compliance requirements need to be managed efficiently. (4/34)
Sara Blakely built Spanx on the frugal prototyping method. The method was simple. Blakely realized that the biggest problem in product development was the tendency to spend too much time and money perfecting a product before testing it with real users. That made products expensive to develop. Expensive development meant less money for other things. Less money meant fragility. Fragility killed startups. (5/34)
Blakely attacked the tendency to over invest in perfection. She created the frugal prototyping method based on one principle: prototype fast, test cheap, learn quickly, iterate. (6/34)
When Blakely developed the first Spanx product, she did not spend months perfecting the prototype. She created a rough version in a weekend. The prototype cost fifty dollars. That meant she could test it with real users quickly. Testing quickly meant she learned what worked and what did not. Learning meant she could iterate. Iterating built Spanx. (7/34)
For an education platform SME, the external compliance problem is the same. The team spends thirty five percent of its time on compliance documentation. That means the team over invests in compliance perfection. Over investing in compliance perfection is expensive. The expense means the team falls behind. Falling behind costs fifty three thousand dollars. (8/34)
Blakely's frugal prototyping method says: prototype fast, test cheap, learn quickly, iterate. Prototyping compliance fast and testing it cheap eliminates the waste. Eliminating waste saves time and money.
## The Core Principle (9/34)
Blakely's frugal prototyping method was built on a simple insight. The best way to manage external compliance requirements is to stop spending thirty five percent of the team's time on perfect compliance documentation. Start prototyping compliance solutions fast, testing them cheaply with auditors, and iterating based on feedback. That turns compliance into a quick feedback loop instead of a slow documentation exercise. (10/34)
Blakely did not manage product development at Spanx by spending months perfecting prototypes and hoping they would work. She managed it by prototyping fast, testing cheap, learning quickly, and iterating. Prototyping fast meant testing with real users quickly. Testing cheap meant iterating without breaking the bank. Iterating built Spanx. (11/34)
For an education platform SME, the problem is the same. The team spends thirty five percent of its time on compliance documentation. That over investment in compliance perfection costs fifty three thousand dollars. Blakely's method says: prototype fast, test cheap, learn quickly, iterate. Prototyping compliance solutions fast and testing them cheap eliminates the waste.
## Four Steps to Apply the Frugal Prototyping Method (12/34)
1. Prototype Fast: Create a Rough Compliance Checklist in Under Thirty Minutes
Blakely prototyped fast at Spanx. Prototyping fast meant she could test quickly. Testing quickly meant she could learn. Learning built Spanx.
You should prototype fast by creating a rough compliance checklist for each feature in under thirty minutes instead of writing a full compliance document that takes two weeks. (13/34)
For an education platform SME, the rough compliance checklist might look like this. The product owner creates a template with five sections. (14/34)
Section one is the feature name. Section two lists applicable regulations like FERPA, COPPA, and state privacy laws. Section three covers data types such as student names, grades, attendance, and teacher notes. Section four lists compliance requirements drawn from the applicable regulations. Section five identifies the evidence auditors will ask for.
This five section template takes under thirty minutes to create. That means the product owner can move fast. (15/34)
Last quarter, the rough compliance checklist was a thirty minute effort. The template was used by the product owner to create a compliance checklist in thirty minutes instead of two weeks. That meant the team spent ten percent of its time on compliance documentation instead of thirty five percent. The reduction saved the company twenty two thousand dollars. (16/34)
For a SAFe team of two to five, the rough compliance checklist should be a template with at least five sections. It should take under thirty minutes to create. For SAFe, it should be part of the team's iteration planning as a planning artifact.
2. Test Cheap: Run a Pre Audit Session Once Per Month
Blakely tested cheap at Spanx. Testing cheap meant she could learn quickly. Learning quickly meant she could iterate. Iterating built Spanx. (17/34)
You should test cheap by running a pre audit session with a compliance consultant once per month instead of waiting for the annual external audit to find problems.
For an education platform SME, the pre audit session is a one hour meeting that happens once per month. It has three parts.
Part one is presenting the compliance checklists. This takes twenty minutes. The product owner shows the consultant the checklists and the consultant reviews them for gaps. (18/34)
Part two is reviewing the evidence. This takes twenty minutes. The product owner shows the consultant the evidence and the consultant checks it for gaps.
Part three is getting feedback. This takes twenty minutes. The consultant tells the product owner what is wrong so the product owner can fix the problems. (19/34)
Last quarter, the team ran three pre audit sessions. The sessions found twelve problems. The team fixed all twelve. That meant the annual external audit found zero problems. The company passed. Passing meant no lost school district contracts, saving fifteen thousand dollars. The pre audit sessions cost three thousand dollars for the consultant. Three thousand dollars was less than fifteen thousand dollars. The sessions were cheap. (20/34)
For a SAFe team of two to five, the pre audit session should be a one hour monthly meeting. For SAFe, it should be part of the team's iteration review as a review activity.
3. Learn Quickly: Build a Compliance Lessons Learned Log
Blakely learned quickly at Spanx. Learning quickly meant she could iterate. Iterating built Spanx. (21/34)
You should learn quickly by documenting every problem found in the pre audit sessions and creating a compliance lessons learned log that the team reviews at the start of each iteration.
For an education platform SME, the log is a spreadsheet with five columns. Column one is the problem. Column two is the root cause. Column three is the fix. Column four is the prevention action. Column five is the iteration number where the problem was found. (22/34)
The log is reviewed at the start of each iteration. That means the team reads it and learns from past mistakes. Learning from past mistakes means the team does not repeat them. (23/34)
Last quarter, creating the log was a one hour effort. The spreadsheet was reviewed at the start of each iteration. The team learned from past mistakes and did not repeat them. The number of problems found in pre audit sessions decreased from twelve in the first month to four in the third month. That learning saved the company nine thousand dollars. (24/34)
For a SAFe team of two to five, the log should be a spreadsheet with at least five columns. It should be reviewed at the start of each iteration. For SAFe, it should be part of the team's iteration retrospective as a retrospective artifact.
4. Iterate: Update the Checklist Template Every Month
Blakely iterated at Spanx. Iterating meant Spanx got better. Getting better built Spanx. (25/34)
You should iterate by updating the rough compliance checklist template every month based on the compliance lessons learned log. That way the template gets better over time and the team spends less time on compliance documentation.
For an education platform SME, the template iteration is a monthly activity at the end of every month. It has two steps. (26/34)
Step one is reviewing the compliance lessons learned log. The product owner reads it, sees the problems, identifies patterns, and determines which problems keep happening.
Step two is updating the template. The product owner adds new sections so the template covers more. Covering more means the team catches more problems early. Catching problems early means less time on compliance documentation. (27/34)
Last quarter, the template was updated three times. Three new sections were added. Section six covered parental consent requirements. Section seven covered data retention policy. Section eight covered breach notification procedure. Each section addressed a gap the pre audit sessions had found. (28/34)
The three new sections made the template better. A better template meant the team spent five percent of its time on compliance documentation instead of ten percent. That reduction saved seven thousand dollars.
For a SAFe team of two to five, the template iteration should be a monthly activity with at least two steps. It should add at least one new section per month. For SAFe, it should be part of the team's iteration retrospective as a retrospective activity. (29/34)
## Closing on Prototyping Fast Over Perfecting Documentation
Sara Blakely did not build Spanx by spending months perfecting prototypes and over investing in perfection. She built it by prototyping fast, testing cheap, learning quickly, and iterating. (30/34)
For an education platform SME running SAFe with a small team of two to five, managing external compliance requirements requires the same approach. Prototype fast by creating a rough compliance checklist for each feature in under thirty minutes. Test cheap by running a pre audit session with a compliance consultant once per month. Learn quickly by documenting every problem and creating a compliance lessons learned log reviewed at the start of each iteration (31/34)