Learning to Respond: Start with Why
Start with Why: Start with why to avoid erroneous leaps in logic and recommend matterful technology change.
Learning to Respond: Logical Fallacies
Logical fallacies: As knowledge workers, we rely on reasoning to recommend an action and build things. A logical fallacy is a flaw in reasoning.
Learning to Respond: Noticing our Reactions
Noticing our reactions: Learning to respond is an essential systems-thinking skill. It begins with noticing our reactions.
Upcoming Events & Experiences
There’s a lot happening in 2023! Here are some events, experiences and books to enjoy.
Making Time for Thinking
Power and control can be nice to have but what we need most is … time to think.
Redesigning Digital Information
Information designed to fit software logic must now be restructured to serve emergent consumer logic.
Emergence
Emergence is a process, the ways simple interactions among individual parts form more-complex behaviors and patterns.
Five Things I’ve Learned About Information Systems
After nearly 20 years, here are five things I’ve learned about (information) systems.
What is Sociotechnical and Why Does it Matter?
We build technology by developing the people who can design, deliver and maintain that technology.
Communication Patterns: Streams
Where once there were events, now there are flows of data published continuously.
Communication Patterns: Events
Events are the way a system communication that something matterful has changed.
Communication Patterns: APIs
As complexity increases, more software parts act as a source of information — with layers that govern communication.
Communication Patterns: Integration
Exploring patterns for forming new relationships between decoupled parts.
Communication Patterns: Decoupling
Exploring how to draw boundaries around software parts. How do you figure out what to decouple from what?
Communication Patterns: Intro
As we move from software to systems of software, time and relationship is where complexity increases at breakneck speed.