Melvin Kranzberg’s “Six Laws of Technology,” are a set of principles formulated during the Cold War era by the historian and technology scholar. These laws were later featured in a Wall Street Journal article titled “The Six Laws of Technology Everyone Should Know” and have become widely cited when reflecting on the complex relationship between technology and society.
These laws remain highly relevant today in many respects, from AI and social media to geopolitical tech competition, and offer a lens to think about unintended consequences, policy implications, and the human context of innovation. And they are relevant to FileMaker.
The Six Laws of Technology
“Technology is neither good nor bad; nor is it neutral.” Its impact depends on how and where it’s used. The same tool can be beneficial in one context and harmful in another.
“Invention is the mother of necessity.” Innovations often generate new needs—e.g., smartphones led to demand for faster networks, accessories, apps, and ecosystems.
“Technology comes in packages, big and small.” Technologies do not exist in isolation—they come as systems or bundles of interconnected tools and processes.
“Although technology might be a prime element in many public issues, nontechnical factors take precedence in technology‑policy decisions.” Political, cultural, economic, and social influences often outweigh purely technical considerations.
“All history is relevant, but the history of technology is the most relevant.” Understanding how past technological shifts (like the Cold War-era systems developments) shaped society helps us meaningfully interpret today’s developments.
“Technology is a very human activity—and so is the history of technology.”
Applying Kranzberg’s Six Laws of Technology to FileMaker…
“Technology is neither good nor bad; nor is it neutral.”
In FileMaker:
FileMaker itself isn’t inherently “good” or “bad.”
It can empower small businesses to grow with custom systems—or it can lead to technical debt if misused (e.g., poor schema design, over-reliance on global variables).
A well-designed solution boosts efficiency. A poorly designed one becomes a bottleneck.
Example: A medical office’s FileMaker-based patient database can either streamline care or cause HIPAA violations if privacy settings aren’t carefully configured.
“Invention is the mother of necessity.”
In FileMaker:
A new FileMaker feature (e.g., JSON functions, REST API, Claris Connect) creates new needs:
JSON brings flexibility—but now devs must learn JSON parsing.
The REST Data API offers integration—but now businesses need authentication strategies and error handling.
Example: Once you give a client a dashboard, they see the value of live data and want more.
“Technology comes in packages, big and small.”
In FileMaker:
A FileMaker solution is rarely standalone. It touches:
External APIs (QuickBooks, RingCentral, Shopify)
Servers (FileMaker Server, Claris Cloud)
User devices (Mac, PC, iOS, WebDirect)
Example: A simple customer tracking app ends up bundled with email automation, shipping APIs, and staff scheduling—all linked through scripts and integrations. It used to be that FileMaker was its own solution; a technology island; not so today.
“Although technology might be a prime element in many public issues, nontechnical factors take precedence in technology-policy decisions.”
In FileMaker:
Clients often choose FileMaker (or resist it) not on technical merit, but based on:
Cost
Fear of change
Trust in the developer
Company politics (e.g., “The IT department doesn’t like FileMaker.”)
Example: A perfectly functional FileMaker CRM might be rejected in favor of Salesforce—not because it’s better, but because the new CEO knows that vendor.
“All history is relevant, but the history of technology is the most relevant.”
In FileMaker:
Knowing FileMaker’s evolution helps avoid past pitfalls and design better systems:
Global fields were once used for everything — now developers use JSON or globals only for session data.
Layout-based printing was key in early versions — now PDF generation and web views are common.
Example: As a developer who remembers FileMaker 4.0, I know the value of modularity and scripted control over reliance on unstored calculations.
“Technology is a very human activity—and so is the history of technology.”
In FileMaker:
FileMaker is shaped by people, not just Claris:
Citizen developers
Consultants crafting niche verticals
Communities sharing add-ons, plugins, and UI libraries
HighPower Data Solutions!
Example: A well-designed FileMaker app reflects the thinking and values of the developer—attention to UI, error handling, naming conventions, and user empowerment.
Final Thoughts
FileMaker perfectly illustrates Kranzberg’s thesis: technology’s impact depends on how humans wield it. It’s not just about fields and scripts—it’s about business needs, developer intent, user experience, and long-term sustainability.
When we design FileMaker applications, we bring the big picture to your solutions. It is not just about writing scripts; it is about providing solutions for the humans who work in YOUR company.
~Dr. William Miller
Founder & CEO, HighPower Data Solutions
HighPowerData.com