Lead With Less Friction: The Design Principle

Every software product has a centre of gravity.

Some are built around features. Some are built around reporting. Some are built around compliance. Some are built around brand.

EthosGov is built around a single principle. Reduce friction at the site. Measurably. Or do not ship.

This is not a marketing line. It is a design constraint. It shapes every decision the product makes, and it filters every feature decision before the feature is built.

Where the Principle Came From

The principle did not appear in a strategy session. It came from the Monash-commissioned SASSLA research, the Invisible Labour report, which named administrative burden as a measurable driver of harm to Principals.

When a body of research documents that a specific category of work is causing measurable damage, a product built for the people doing that work has to take a position. Either it reduces the identified burden or it is part of it.

There is no neutral option.

EthosGov took the position. Every feature has to justify itself against one question: does this reduce friction for the people who are already carrying too much, or does it add to it?

What Friction Actually Is

Friction in a public school is specific. It is not abstract overhead.

It is the ten minutes lost to logging into four different systems to answer one question. It is the hour spent reconstructing an incident timeline because the record was scattered across email, SharePoint, and a notebook. It is the Sunday evening spent assembling a Council pack because the week was consumed by actual work. It is the second phone call required to chase an overdue risk assessment because the tool did not surface that it was overdue.

These are the minutes that invisible labour is measured in. They add up. Over a term, they become hours. Over a year, they become the difference between a sustainable role and a burnout one.

Reducing friction means attacking those specific minutes, concretely, with design choices that return them to the Principal, the Deputy, and the Administrator.

What It Does Not Mean

Reducing friction does not mean simplifying governance. Governance obligations are what they are. The state has set them. The Department has framed them. The policies exist. The risk has to be managed.

Reducing friction means carrying the same weight with less cognitive and operational overhead.

It does not mean hiding complexity. A tool that pretends the complexity is not there fails as soon as a real audit arrives. The complexity has to be handled. The handling just should not fall on the Principal's shoulders personally.

It does not mean automating judgement. A tool that tries to replace the Principal's decision-making with an algorithm will be rejected by the sector within a term, and deservedly so. Judgement is the core of the role. The tool's job is to make judgement possible, not to replace it.

The Net Logins Test

One concrete design test: does adopting this tool reduce the net number of systems the Principal has to log into, or does it add one?

If a tool is proposed that sits alongside existing systems, the answer is net additional. Rejected.

If a tool replaces one or more existing systems, the answer is net neutral or net reduction. Acceptable.

The Principal's desktop is already crowded. Four tabs minimum. Six is common. Ten is not unusual. Any tool that adds a tab without taking at least one away is failing the friction test at the starting line.

EthosGov consolidates. It replaces the compliance tracking spreadsheet. It replaces the incident log Word document. It replaces the risk register that lives in its own file. It replaces the Council pack assembly process. It replaces the reconstruction work that happens before every Departmental submission.

If it does not, it has not earned its place.

The Measurement Discipline

Claiming friction reduction is easy. Measuring it is harder.

EthosGov is building the measurement discipline into the product. Time saved per cycle. Number of systems replaced. Hours returned to leadership work. Before-and-after documentation on cycle time for specific artefacts.

This measurement is shared with the customer. It is shared with the Department. It is shared in case studies. It is not private marketing data. It is the point.

If the measurement shows no reduction, the feature or the deployment is revisited. A product that claims less friction and does not deliver it fails the only test that matters.

This is a discipline that takes time to build. It is being built anyway, because it is the only evaluation framework the sector should care about.

The Design Choices That Follow

When the principle is held consistently, specific design choices follow.

One login, not many. Every module of EthosGov is accessible from a single authentication surface. The Principal does not log into Lead, then Improve, then Assure, then Oversee. They log in once.

One record, many views. Incidents are logged once and seen differently by the Principal, the Deputy, the Director and the Department. The record is not rebuilt for each audience. It is recomposed.

Actions that follow the work. When a leadership meeting is held, the action register is already integrated. The Deputy does not transcribe actions from minutes into a separate tracker. The surface is the tracker.

Alerts routed, not chased. When a compliance obligation approaches its deadline, the relevant owner is notified. The Principal does not carry the calendar in their head. The system carries it.

Reports composed, not assembled. Council packs build themselves from existing work, reviewed by the Principal before release. The preparation time drops from hours to minutes.

These are not unique ideas. They are design choices that follow from holding the friction principle honestly. Most tools do not hold it honestly, because the internal incentives to add features usually outweigh the internal incentives to reduce load.

What It Takes to Hold the Principle

Holding a friction principle is harder than declaring one.

Every customer conversation produces feature requests. Every Departmental engagement produces reporting asks. Every competitor launch produces pressure to match. Every investor conversation produces scope expansion suggestions.

The principle holds only when it is the default decision rule. New feature proposed? Does it reduce friction measurably? If yes, build it. If no, do not build it, regardless of how compelling the argument is.

This is a discipline the team has to hold internally. Customers will not hold it for us. They will ask for features that do not reduce friction. That is rational on their part. It is the team's job to hold the line.

Over time, the customers who stay are the customers for whom the principle is the primary value. They are the ones who will recommend the product to other schools, not for a specific feature, but because the load on their desk got lighter.

That is the dependency the product is building.

The Signal to the Sector

One subtle consequence of the principle.

When the sector sees a product that is holding a friction-reduction line consistently, it changes the expectations for the next generation of tools. The bar goes up.

If EthosGov succeeds, the next wave of public school software will be judged against the same standard. Does this reduce friction? Measurably? Or does it add to the load?

A higher bar for the sector is a net good, regardless of whether EthosGov is the tool that gets adopted. Sector-wide friction reduction is a policy outcome in its own right.

That is not marketing. That is the point of doing this.

Take the Next Step

If this article speaks to your situation, two routes from here.

Go deeper on the verb. Read the Lead cornerstone. It is the deep page that sits underneath every article in this category.

See it on your site. Book a Governance Review. 45 minutes. No deck. We measure what the friction is costing you and whether EthosGov reduces it measurably.

---

Part of the EthosGov resources library. Governance infrastructure for public school systems. Lead. Improve. Assure. Oversee.