A Trace in the Sand
by Ruth Malan
This Trace is just where I jot notes as I explore in and around the territories I associate with architects architecting architecture. Since I work with architects across the spectrum from applications to enterprises, the scope of my exploration flexes accordingly. For a playful orientation to this Trace, you can read the characterization I assembled here, or selection of posts I assembled here, or visit my in-progress Journal Map.
May you be this happy!
Given that the contribution and relevance, even the very future, of EA is oft called into question (the latest prompt being here), you may be interested in bringing some exposure to EA as a source of strategic advantage:
One of our clients has won the Enterprise Architecture Award, and architects from at least one of the other winners have taken our EA workshop. Naturally, while we can't claim any credit as they did it all themselves, I do think it is a marked demonstration of excellence to choose to work with us. ;-) As you know from our papers, our orientation to architecture is very much about enabling strategy.
With ever increasing complexity and wave after wave of change, I believe the question is not whether EA will continue to be relevant and essential, but whether we can get a strong enough handle on it ourselves, otherwise it might have to make its contribution under another name because we flub this one/cause it to develop #fail antibodies! Truly, I am not in the least bit worried about the need for all manner of systems design expertise. We -- we digital/compute/technology types -- are reshaping the landscape of business. Not because people don't matter or aren't central to our concern. But because we amplify what we can accomplish, we augment our capabilities, with our tools, including tools that connect us. And we speed the evolutionary process by which we reach better fit to context and co-shaping and co-evolving purpose and system through experimental, iterative, feedback-intensive design. Aesthetic and structural design, for these go together to produce integrity. And design is riding an awareness wave right into the executive suite. So, surf that wave with what Jeanne Ross has to say about EA in Busting CIO Myths (April 29, 2012), and follow it up smartly with Fractal and Emergent. :-)
Wave after wave of change? Here's a sampling of what we're doing:
We're changing the world, weaving digital ever deeper into our organization's capabilities and that weaving, if we're to achieve more the outcomes we want, needs to be designed*. And because it's complex and we're not all-knowing let alone prescient, it behooves us to consider the feedback on experimental design nudges and adaptations and further adapt and learn. All the matter of enterprise architecture as an adaptive, evolutionary, part-intentional part-emergent process that partners closely with strategy. Which is to say, a key part of what we do is design feedback loops into strategy, and those too need to evolve!
And because we're the stewards of such massive reconfiguring of society, we need also to be careful to take into account sustainability in all its forms, including environmental, social and economic. Reading in the ecosystem thread on my ongoing investigations, I thought this was interesting:
We're going to make interventions into the webs of life on this planet. We just are. Too many people, each of us aspiring. So, we need to get smarter not just about our cities but our organizations, our farms, everything. Enterprise architecture is about attending -- studying, designing and adapting, reconsidering, adjusting, aligning, evolving -- interwoven, interacting, enterprise socio-technical systems that extend within and without the organization. Big stuff. Strategically critical but by no means universally understood to be, and hence a great source of strategic advantage to those who get it..
5/2/12: Well, it's ugly when someone -- especially a "lady" -- says "I told you so" but really... this is so "like we've been saying":
Except that we've also been showing how to do that for a decade! Of course, you can take this as a challenge to go back to our What it Takes to be Great and EA as Strategic Differentiator papers to verify that my claim is accurate. ;-)
Oh, I well know that others, including Tom Graves, have been doing likewise. Goodness, what is low hanging fruit for if not to pick? Now, as low hanging fruit goes, Gartner hung out some really juicy ones with that article! To be effective, we have to change our focus from deliverables to outcomes. Sure, sure, there'll be dashboards and even blueprints, etc., where needed. But if we don't focus on outcomes, we're not asking ourselves that crucial "what is the most important..."
Oh my, this is indeed not the most important thing for me to be doing at this extraordinary moment! I have a deliverable to turn in! Ta ta! ;-)
* At different (fractal) strategy and design scopes, and sometimes with more intentionality, and at others allowing emergence to reveal patterns and yield outcomes we learn from before adapting intentions and designs.
Image: By Sara B.
Architecturally significant? Well, goodness me, you view yourself as a leader, don't you? You want to achieve system integrity that is as if of one mind, right? Well? Guess what's coming -- you'll learn the lesson all the more thoroughly!
And you wondered why I ask so many questions about what I am about to say next? Ha! But ooh, now I know how to position my habit of not finishing sentences. ;-) Ah yes. I wonder what rhetorical fallacies I've leveraged here?
* Hey, the advantage of Tracing is memory enhancement -- I just have to remember what I noted, not where I did so because googling my site gets me to where (try "metaphor brain site:ruthmalan.com" and see the first result). More seriously, Tracing is a process of reflecting:
though I like how Daniel Stroe put it:
Here's an example of considering something from an interesting angle:
Keiretsu and ecosystem weaving. Still no interest in what I'm up to? Look, tell you what. We won't fire me. We'll fire you. Oh, ok, we won't do that, but, goodness, you could be a little encouraging now and then! It gets lonely out here on the ecosystem branch with only faint indirect voices to be heard over in Cannes and other places. ;-)
5/3/12: See also: The Storytelling Animal: The Science of How We Came to Live and Breathe Stories, Maria Popova, 5/3/12
Those are useful posts, though I was struck by "People talk about different platform strategies, using terms like "open" and "closed", but these terms seem to have worryingly unstable meanings." Well, while we IT folk tend to think we need to nail down definitions and standards (and we do, when it comes to interoperability, but much more arguable when it comes to process), the strategy folk aren't nearly so concerned to all speak from the same playbook. They each write their own. And its a good thing Apple didn't listen to Clayton Christensen's version... Which is not to say Christensen isn't right when he's right*, just that the name of the game in differentiation is creating differences that make a difference. That said, it seems to me that a "walled garden" lies between open and closed, and that part of the "instability" has to do with there being a spectrum (perhaps even a multidimensional space) of platform strategies. The insight to tease out of Richard's unease probably has to do with getting more of a handle on what that spectrum or space is, and I think that would be useful!
Anyway, I've been using the term relationship platform because, well, it's an architecture thing -- it's about enabling relationships (value flows, information flows, interactions and engagement, etc.). But that's just me running up my strategic flag, marking it architecture territory. ;-)
* Huh? Oh, that's just my coy way of giving Christensen no more than his due. ;-)
5/8/12: See also:
5/10/12: Richard Veryard has collected together a very useful set of pointers to platform strategy articles.
Daniel Stroe asked me about the role of fashion in tech and I could see a blog post percolating there. Well, I'm waiting Daniel! :-) In the meantime, I think he is definitely onto something worth exploring. Does the itch instigate fashion or fashion create the itch? Whatever. Robots (and other forms of AI... not all have appendages, etc.) are emerging throughout the realms of our experience from the phone we carry to our homes and workplaces ... and space station. And we're intrigued and drawn to what they enable, for in important ways they extend and enhance us, improve many aspects of our experience.
They march into our lives with a shadow side. There's no going back. But we simply have to be more attendant to our civic and corporate responsibility in terms of people who are being sidelined by robots.
We are tantalized by robots. The itch is our own aspiration.
I know, I show up too much here as myself, and that puts people off. But I believe we need to shape a world where people care -- more, not less! If we don't, what is there? We plug our heads into our devices and simply make informational connections to others, with no caring? That is a route to dystopia. We need to shape a world we want to live in! (Apologies about the language but this is just perfect for this moment we're at, isn't it)
So, sure, I challenge the notion that our online presence should be sterile and flat, emotionless and business-mechanical. Do we want to rouse humanity out of the industrial-machine era? Doesn't that mean investing in building stronger community bonds that move caring not just information around?
The way we're going, teaching robots to detect emotions and appear to respond appropriately (even with humor) while we wash so much of humanity into conformity and dullness, we'll get to the point where that becomes "The real problem is not whether machines care but whether men do."
We do need to be concerned about our social schisms. Including the exclusivity of software... and the dearth of women in our field.
5/4/12: My son's documentary, We Know, We Care, is done! He's hoping it will be shown on the community access TV station he's been doing volunteer work at this past school year. Kids are so amazing! Like this: Tavi Gevinson: A teen just trying to figure it out. Showing us how to illustrate with flair, no artificial societally-imposed inhibitions restricting communication effectiveness.
I told ze boy about John's tweet. He was taken aback by the language (moi? Is he the only person in the world who avoids such language? I once explained that I prefer to avoid the f-word because it has roots in sexual aggression, and until we're done with sex being used to dominate and aggress, my small protest is to hold my own inner boycott of said explicatives. Eh. That's just a rationalization. Really I'm just a prude. Ha. Gottcha.)
5/8/12: Seth Godin's post on Caring got a fair amount of Twit-play the other day: A simple antidote to a corporatized, unfeeling, profit-maximizing world Care. I really liked the phrase "Caring gives you a compass". Anyway, I thought this was interesting:
Introverts are social creatures too. Who knew? ;-) But more:
For those who haven't been reading along here for the past several years, and on the assumption that you have some interest in the perspective we share, what follows is a sampling of our approach to being agile in system concept exploration and development:
And if that has whet your appetite, you may be interested in Software [Creation and] Engineering, 10/5/11.
You might also be interested in the section on Visual Thinking and Visual Design on my Trace map (my inner critic has already told me that section needs a sub-structuring/re-ordering). There are also posts like Testing on Paper collected under Improvement and Validation. Now you might react with "that's just the message in pretendotyping" or some such, but Visual Architecting long predates but also goes deeper than pretendotyping.
In Visual Architecting, we take the approach of exploring the "problem" and "solution" together -- tackling the dominant uncertainties and challenges of the moment. A well understood (next generation) kind of system has different challenges than systems that are defining value in an emergent ecosystem (niche). We need to adapt and flex to the design (organizational and technical) challenges of the context and the moment.
And I offer a different lens, now don't I? It is interesting how people who characterize themselves as curious may have quite settled notions about authors they'll find useful or "relevant."
But, as different lenses go, this is a nice post:
And as perceptual traps go, this is also useful:
Well, right then. I'm going to extend the early enrollment discount by two weeks so let's fill this workshop in Chicago in July! It's fun. You're fun. Let's do it!
I prefer to be your advocate, but... a workshop is great when great people participate, so I suppose I have to swallow all my history and see if this self-promotion thing works. ;-) It's lousy when one is one's own product*, it really is! Especially if one is a Q<= in which case all kinds of social forces come into play to make that very hard to stomach!
That said, in truth, if anyone who read my Trace, or knew someone who read my Trace, came to a workshop I was leading, I'd have such bad stage fright and be so self-conscious it would be altogether terrible! One really doesn't want to actually meet the people who have read her mind -- that would be, like, embarrassing! I mean, by reading here, you have so many opportunities to think me an idiot, to disagree with me, or to... think I'm pathetic. So no, I don't want to work with you either. Well, not unless you admire what I do, and get value from it. But how unlikely that is!!!
Further, if anyone says something nice about my Trace after I've done one of my imperious "I need a pig here" things, I discount that entirely! To be taken seriously, appreciation has to be genuine and so has to be spontaneous.
'* Actually, I have to confess, architects are my "product," and what I have to sell is you, with whatever you inspire and enhance in yourself given the crucible we convene and create together. Which makes it all the more of sticky business trying to "sell" what I do! ;-) Unfortunately our dominance stacked world has told all of us that you should only attend to me if I come across as an authority, meaning I "mark the territory" as mine (including "positioning" and framing," which too often amounts to deriding what others do), lay claim to fame, that sort of thing. And I come along and tell you I'm here to convene dialog and draw forth from all of our experience and the interaction of our knowledge, insights and capabilities, and provide some context awareness, conceptual models, heuristics, etc., and facilitation to outcomes, but really you have the lead role to play in what you learn and make of what we do together. So, yeah sure, I act as a coach and provide a semi-structured crucible so that the workshop has flow (in multiple senses), and there are even times when I teach, often in stories but in various forms. But really you are the principal agent of your own self, and sure, I serve to add some new blends into your cognitive and experience streams, but more importantly, I help you see what you already have to work with, and remind you that you have to do the weaving, the selecting, responding, to create the great living tapestry of your becoming. But no, I don't say that! Instead I tell people we're rafting down the Colorado and it's going to feel pretty wild at times but I've taken many groups down this stretch and while it has been different every time, we'll get through so have fun. ;-)
Daniel Stroe kindly suggested I do something like Alexander Osterwalder's Business Model Theater, since what we do is highly visual and has a small set of neat conceptual organizing frameworks. Well, of course we'd have to use Dana's cool radio-quality American male voice. My South African Q<= voice is... not very commanding. (One workshop someone flat out asked where Dana was, and that actually flipped the dynamic and several architects in the workshop became really active advocates of my style and message.)
5/25/12: It really is an enabling, empowering, mindset shifting, career enhancing 4 days that is well worth the time and budget allocation. This is one of those rare ways to invest time to amplify what you achieve. You have only this one life to make a big difference to the experience of people and the other inhabitants of this planet. And this workshop is all about making a big difference by working more effectively with and through other people to create great socio-technical systems.
Ok, the list -- I need to clean it up, but here's the 1 minute core dump. First, there are a good number we share on Tony's list:
And some from "avatarmysti"s list (comment on Tony's post):
I haven't mentioned the Daoists and philosophers... I'm tempted to mention Joseph Campbell (myths)... the list just gets longer! The likes of Donella Meadows, John Holland, John Seddon, John Gall and Jerry Weinberg have influenced my thinking, but so has Grady Booch and it gets harder to draw the line as we transition from "founders" and early classical works to the current set of influencers. For example, Jamshid Gharajedaghi (Ackoff's heir apparent at Interact) perhaps warrants mention.
Now I need to investigate Rudy Starkermann, John Warfield, Bill Livingston, Thornstein Veblen, Francisco Varela, Heinz von Foerster, Stuart Kauffman, Pille Bunnell, George Spencer-Brown, Louis Kaufmann, John Wheeler, Buzz Holling, and Benjamin Lee Whorf.
I guess I'm going to have to put in an order for at least another life!
5/6/2012: Bob Marshall has also created a gallery of giants (overlaps with, but not limited to, systems thinking). Nice to see the inclusion of Tom Gilb.
2/19/15: And these, from Mark Burgess, related to complexity:
When I read Avivah Wittenberg-Cox's HBR piece, I wondered if the difference has more to do with being decades in to the big shift -- a shift in the gender distribution of the workforce coinciding also with the weaving of digital through so many (approaching all) facets of life and work. Consider digital and sex. I mean sex, not gender, and Zimbardo's point about how that is reshaping youth culture -- for boys, and for girls. So we have all kinds of identity shifts going on, and it raises questions for me. Like, is the techchismo element in our field there because it is a defense mechanism in a world that is shifting in ways that make it uncertain, so that one strategy for defining identity in an ambiguous, socially challenging and changing world is to form elite tech-tribes where camaraderie among the cohort is super-strong? And exclusive.
When I was an undergrad, CS and math were pretty evenly split between men and women, and no-one suggested women couldn't or wouldn't want to do CS. There wasn't the gap then that there is now between those who programmed in middle and high school and those who didn't. Now there's a big gap. And I fear that it is like music -- kids who began taking music at a young age don't just have years head start on kids who come to it late, but their brains are different. I think that is a research area that should be something of a priority. Regardless, we should give more kids -- boys and girls -- more exposure to developing software in non-threatening settings (I don't just mean without the chismo element but where the entry-hurdles of development environment are low and the kids can just get started doing stuff that works. There'll be endless hassle-battles with the development environment thereafter, to develop that skill. Sadly.).
Of course it's not just gender distribution that shifted from pretty even when I entered software to heavily skewed. There is a sense that social changes are afoot, riding many trends including widespread higher levels of education, more technologically-enabled connectedness that puts distributed people in touch, .... So this is interesting:
As is this:
Which I contrast with this:
There's flocking and self-organizing which calls to mind:
A changing world. And I expect we are in the throes of multiple mass social "identity crises." For example, there is the crisis of consumer confidence that has something to do with the economic shakedown that continues to send global tremors, and indeed deep system shocks, but which also has to do with climate change. On the one hand, our material and technological aspirations serve to keep the heat turned up in globally interconnected economies. But the sense that the "American dream" (easy to call it that, but it really has not been localized) has been paid for in climate change and increasing damage there-from, puts us in a damned if we do, damned if we don't sort of situation. It'd be great if the likes of GE would "do an Apple" on the world and transform green energy into something as aspirationally trendy as other tech gadgets consumers crave and stretch budgets for, so we can, in turn, indulge our dreams from travel to tech-toys and extensions of our minds and....
Because we do stand at the portal to such an exciting world! Sara had this dream where she woke up from a wonderful dream but couldn't remember any of it, but they'd invented this technology where she could just replay her dream. So in her dream, she replayed her dream. She told us that, and of course my imagination took it the next step -- in my hallucination of the future, dreams will be entertainment and some people will become known and sought for their dreams. Daydreams too, but dreams because they are so rich with visual imagery as well as inconceivable (in grounded reality terms) drama and invention (social, biological, and in Sara's case, bio-technical). Reality TV of the future... As for transportation, my 1 minute fantasy stimulated by this provocation, was separating "cargo" from "person" -- send our groceries home on robot dogs and run or fly in superman suits that give able-bodied people what we're gearing up to give people who have lost limbs or nervous system function. Make us run like the wind, and who'll want to drive? That'd sure put a rush in rush-hour. (grin)! Put safety sensors and controls in those bat-suits people jump off cliffs in, and we can jump off skyscrapers after work and fly home. All kinds of radically cool stuff out there in the (near?) future! I know, it sounds far fetched, but can't you see compute, nano and biotechnologies not only enhancing our individual and collective intelligence and the mobility and fine motor skills of robots, but enhancing and amplifying our bodies too? Come on, come on, just put me on the job. ;-) Me, and anyone else with two minutes worth of imagination!
If we want to create more a world of mutual enrichment rather than destructive competition, can we look to those who know how, and prefer, to work with and through others to right wrongs and advance our civilization? Should we stop decrying the fact that there aren't enough assertively competitive command and control sorts of women and begin to be heartily relieved that ever so many women and men are indeed well equipped and ready to lead, in pulsing shifting-to-suit-the-moment ways, us to being effective within a quite different kind of power structure? Where leadership, as in the family structure, isn't a charge but taken on fluidly, as suits the temperament and skills and availability and more of the moment.
5/7/12: Skinner Box? There's an App for That, Jim Stogdill, 4 January 2010
5/9/12: John Hagel on what he terms masculine versus feminine archetypes:
It might be useful to put this (as Tom Peters has) in terms of dominance-hierarchical versus network-facilitative styles so that it isn't directly connected to gender (although there are strong gender proclivities, which are at least in part socialized or socially reinforced).
5/14/12: The uproar over Dell/Mads Christensen may serve to bring needed attention to several plights:
5/17/12: I do wonder if anyone is researching the connection between tribalism, dominance behaviors and social hierarchies, and the outcroppings of these kinds of things at tech conferences... Danah Boyd's work on bullying, for example, seems to have some application, and she's pointed to the social hierarchy aspect to bullying...
This, too, via Michael. The man is founder and supreme ruler of a new paradigm of twisted* intellectual nerd comedy that uses Twitter as a platform for broadcast and improvisational comedic engagement.
* I mean that appreciatively!
Son (14 y.o. wisdom): "Any photo is an image. A good photo captures a moment. A great one tells a story."
I shared this snippet with Dana:
The hero doesn't just see the world he returns to differently, but is able to see differently. That distinction resonated, for example indicating the difference between the diagnostician who has great knowledge from the master diagnostician who uses perception in arriving at an accurate diagnosis. That is, one has attained mastery when one has moved beyond knowledge to developed perception. Not just a different perception, but an enhanced capacity for perception. The hero's journey is about moving to a different vantage point on one's old life, seeing it from a new perspective, with some detachment and the perspective of other experience, encounters it with altered perception. Dana pointed to the Sufi concept of organs of perception, and he added that that is what real education tries to achieve -- to develop perception, to develop the ability to shift perspective, to see what others don't see and to see more penetratingly and discerningly.
Clusters and City Ecosystems
Value Flows and Ecosystems
Here's a piece from my 12/01/11 Trace:
The Power of Visual Perspective
Tools We Use, and Those That Use Us
Achieving Flow: Matters of Scale and Growing Up (or Out)
As things centralized/decentralized go, this caught my eye:
Here's the tweet -- it points to a bit I wrote on Enterprise Architecture and capabilities back in 2003! I had so totally forgotten about it! Don't you like that "small teams operating with sufficient autonomy not to be stifled by the corporate blanket"?
5/16/12: I've mentioned Stuart Boardman's posts on ecosystems over the past few months, but it is probably worth collecting them together for ease of reference and to give you a handle on someone else working in this "ecosystems and EA" space:
From our Family's Hero
Read bottom, then top, then middle (it's Twit-formatted):
But there's always time for Twitter. ;-)
I followed Notch and a Minecrafter immediately followed me. I've been hanging out in the wrong crowd! ;-) I guess being a cartoon-head with architecture on the mind doesn't convey sufficiently in the architect set... Sigh.
Ok. So I like to find interesting people to follow. Sometimes I already know they're interesting, as in the case of Notch because I like to keep tabs on paradigm shifters in the software space. (Minecraft is a wonderful example of how ecosystems spring up whereever there is a rich relationship firmament to grow on. And decisions made by Notch and his team keep surprising me. The whole redstone thing, turning a game into an electronics lab, is genius. As is the whole kittens thing. Etc.)
And, according to Simon Gough's follower diagnostic, I'm BORING. Oh wait, that must mean he's WRONG! ;-) Or not. But this is my rationalization: I'm more curious than other people. CURIOSER. Not Boring. Ok? Alternatively, one could say: that I am labelled as boring in our field is an indicator of gross discrimination against cartoonheads (it couldn't be women, could it?). Wink. Just kidding. (It was throwing my lot in with architects. And worse. enterprise architects. Wink. Oh. I am kidding. Really!) I take it as a point of pride to stay well ahead on curiosity. Q<=s are very competitive, just perversely so. ;-) If we turn hierarchy upside down, women will be on top.
5/14/12: Anyway it's not how many followers, but who they are, right?
We have reconceived "social" in the age of digital connectivity, and it is driving a "big shift":
And the shift is hitting the software development fan:
(Sorry, couldn't resist the word play. Of course, Shift Happens is old already, but it gets a whole new spin when it hits the fan...)
One of the distinguishing responsibilities of the architect is identifying and designing mechanisms for system integrity and resilience (and other sustainability factors).
Amory Lovins: A 50-year plan for energy, TED, March 2012:
There is so much in that talk of note! But. It's late. If you take notes while you watch it, send them to me and I'll add them here. ;-) (I was working out; oh hm, I need to triple task and take notes while I watch and work out...)
Why do I say that's a must read? Think architecture. ;-)
Oh, yeah, have you read "What it Takes to be a Great Enterprise Architect"? Have you recommended it to others? Well, why ever not?
And, to make sure your information diet has a suitable mix tonight, Martin Fowler's OrmHate piece is worthwhile.
Given the introduction to Managing as Designing, I'm excited to put it on my "up next to read list"! It addresses managers, but could just as well be addressed to enterprise architects and senior software architects and... well, if it is as good as it promises, I'd recommend it to any architect in IT and product development but not all would thank me. ;-) Then again, not all would a priori know to thank me for a pointer to Argyris or March. Still, those who (come to) grok that the non-technical aspects of the role of the architect really rachet up when organizational scaling issues mount (so one needs to do more with and through others, more effectively) will (come to) recognize the value.
SATURN2012 from the Sidelines
This one served as a percolator (surfacing a tacit understanding) for me:
Architecture is the vehicle* for value, not a trade-off against value. Of course I get that the issue being dealt with here has to do with the tension between unarchitecture (quick and dirty get it working) versus refactoring and just enough design for structural integrity and sustainability, including sustainable team flow. There is no quick-fix for judgment. It has to be developed. Experience factors (and refactors).
Wow, two years have passed since I presented The Art of Drawing People In tutorial at SATURN! I've much enjoyed encounters with various people on the SEI team and they draw a great community together. And it's fun being on both sides of the conference firehose. Last time I was only able to be there for the evening before my tutorial but at least I had the chance to have dinner with Olaf Zimmermann and George Fairbanks and a couple of architects whose names (hit me) I don't remember. Well, maybe next year I'll summon the audacity to submit the Something About Boxes tutorial again. Wink. Though perhaps I may frame it in more conventional (in-the-box) terms. Grin. Perhaps I should reign in my playfulness... (Really, if you don't get me, you could watch Funny Girl. Then it will all fall into place. Or, if the pace of the movie frustrates the thoroughly modern you, I'll cut to the chase and say Streisand's character uses making fun of her own weak points to take that arrow out of the quiver of her detractors. Of course you have to understand that she could not do this if she wasn't absolutely confident about her strong points; she is spunky because she has a strong foundation.)
* delivers, is a conduit for, shapes and enables
I was surprised to see the following apparently attributed to Len Bass:
This is from the Software Architecture: Central Concerns, Key Decisions chapter (in the Software Architecture Action Guide draft) we wrote in 2002:
But then I reread our Less is More with Minimalist Architecture paper published by the IEEE in 2002, and perhaps I left room for someone to mistakenly attribute more of what I wrote there to Len than "'these decisions identify the system’s key structural elements, the externally visible properties of these elements, and their relationships' (Len Bass, Paul Clements, and Rick Kazman, Software Architecture in Practice, Addison-Wesley, 1997)". But it does remind me, if you hadn't read it, you might be interested to -- as you can see, given that our guidance in that 2002 paper was an important part of a keynote in 2012, we did pretty well. ;-)
Rereading Less is More, I'm relieved to see that it mostly stands up well to the test of time, though I'd change some of the phrasing if I could. ;-) For example, there are antibodies to the word "asset" now that I'd avoid setting off -- though as you well know, I, and others who talk about people as assets, do not mean for it to be interpreted in mechanistic-economic terms! [If I say my writing skill is my best asset, I don't mean it is at my command...] Sometimes people can get upset at a word, because they are opposed to something else in the context -- for example, where there is an orientation to treating people like things that can be hired and fired without thought to the personal consequences then the asset word carries that negative spin. And so forth. Naturally that is very far from my orientation. So I hope people read the paper with goodwill enough not to be rattled by a word here and there. :-)
Of course I have learned a lot in the interim decade, and all I have learned is to be credited to the architects I have interacted and worked with -- those who have mightily disagreed with me actually perhaps less than one might think, for it is in respectful peer discussions that I am at my most productive and resourceful and most able to do an about-face and see things from a new vantage point. With reference to the specific paper, I would put more emphasis on the left hand-right hand image and the importance of working through cultural mechanisms not just through decisions -- the message is there, but I would highlight it more. We have emphasized decisions a lot in the architecture field, but they're not the full story. ;-) Again, there we are somewhat to blame, for our Software Architecture Decision Model is a peer (circa mid-90's) model to Philippe Kruchten's more well-known 4+1 View Model. Philippe had the good sense to publish formally, while I was early to the Internet band of free and open access -- I created and was principal writer for the Fusion site (and published the Fusion Newsletters online) and then the HP Software Architecture site and later the Bredemeyer site through the 90's. Well, all that is merely of passing note. Let me return for the moment to my criticism of my 10-year ago self and what I wrote in that short paper: I would also do a better job of framing the context (considerations about scope -- architecture for complex system or for family of products, etc.) for what I had to say.
The neat thing reading that work again is that it has held up rather well. I believe we have learned a lot, and I would cast some things rather differently, but it is good to be reminded -- especially comparing what we were saying, teaching and writing then to what others are saying now -- that we were leading. Alternately put, we need to get the book that reflects the current state of our understanding written. So that I can look at it in ten more years and wince in parts and be relieved in others to still be relevant and useful. Hopefully. ;-)
One of the things we've been doing differently since that chapter was drafted in 2002, is more explicitly address uncertainties, challenges and risks. Sure, this shows up in that earlier work (for example in priority setting), but under the influence of Charlie Alfred we made it a much more explicit part of the process. Some of what we learn is about emphasis, and framing (how we articulate the importance). [Using Architecture Challenges To Formulate Software Architecture Published: Mar 19, 2003] Anyway, hats off to Charlie. Take a bow Mr. Alfred. :-)
Oh, as things "meta" go, Dana pointed me to this: This Story Is So 'Meta', npr, May 5, 2012.
That was random. ;-)
5/15/12: I've learned a lot from Charlie Alfred -- follow him! Oh, I mean, why don't you consider following him? :-)
5/22/12: See other architecting across concept sketches from 2008 (the year Archman was "born").
I've been working on advancing what we do in the ecosystems space, to create models of what is changing in the business world as it is reinventing itself with a fundamentally digital -- rather then human-organic -- nervous system... one where human brains plug in like nodes in the organizational brain... Yes, I pitched that in provocative terms. Still, I do think that there is an important insight there: the big disruption is the disruption of people -- we are ever advancing the realms of work we automate and displacing jobs to digitally-intelligenced machines at a rate that is overwhelming society and sending shock waves through our economic and socio-political systems. I think we need a handle on that, and what it means for society. That sort of thing.
But I'm trying to characterize what is going on here, in the organization and the ecosystem, so I can help our field advance -- figure out how to adapt what we do in our modeling work, what is a minimalist view of what we characterize for strategy and architecture so the integration is sensible... (that is, sense-able and sensible)... So, yes, this is a very intense research phase and if I give you a glimpse of what is going on in the head-space I can share, this is what you see.
That said, I see what I am doing more as "architecting the space" -- the models we use to understand a space shape it*, they shape what we see, hence what we act on... so understanding the structure and dynamics that underlie business ecosystems, strategy and enterprise architecture is wickedly important, wickedly hard, and wickedly engulfing! Right? Just like the size of rocket boosters on the space shuttle was dictated by what trains could carry, dictated in turn by horse-drawn wagons going back to Roman chariots, the mental frames through which we view the world determine in important ways what we are able to see -- and what is occluded. Our thinking frames become ruts. Simple frames are immensely useful. And they limit. Not that I allow myself to be too self-important here, for there are many perspectives. Nonetheless, it is work I feel requires a responsible orientation.
I want to be beyond this research phase, I really do! I'm desperately hungry to switch gears from direction finding in the ecosystem/strategy/EA space to tunneling down in writing code -- I like the interactive feedback loop with computers, and we're designin/prototyping the next big thing which is so exciting! But I need to feel that what minimal pieces I put together to inform strategy and EA from the ecosystems vantage point are useful in helping to create architectures that are "good, right and successful" (a term Dana Bredemeyer coined as a catchy memory hook for architectures that are technically sound -- good; meet stakeholders goals and fit context and purpose -- right; and actually deliver strategic outcomes -- successful).
We take big complex soup and boil it down to a simple just enough "scaffolding" that helps those who work with us create great systems. You see me grappling with the soup -- the interwoven mess of a business world in tremendous flux. Perhaps I should hide that process. I certainly don't want the grappling to diminish how you view the results I draw out. The simple models and relationships, the crystals of vision.
So I like to think that what I do is "advance frontiers" ;-) But "fomenting a philosophy of technology" captures a dimension of what this Trace is about. Mainly it is about the architecture of architecture. Characterizing its identity, its differentiating value, the capabilities that allow that value to be created, enhanced and evolved, the design of design. And architectures evolve. So yes, I explore that evolution here.
Image source: Bits & Chips, Stoomcursus systeemarchitectuur
* Shape, or at least influence. As do the terms we use -- Sapir-Whorf Hypothesis.
Thank You to Kris Meukens for the #follow friday. :-) I value the goodwill and expression thereof, and I'm grateful for the thoughtful gesture of community building. A gesture of reciprocal goodwill would include, for example, following Kris.
As following goes... my Business Ecosystems and Characterizing Change Pinterest boards are coming along nicely, don't you think? (Btw, Pinterest won't grab an image from some sites -- such as Stuart Boardman's Scrbd insert on his Metropolis post. Just so you know I wasn't ignoring Stuart. ;-)
Leaky Networks and Serendipity
The paragraphs below, from Frank Duffy's wonderful article "Lumbering to Extinction in the Digital Field", struck me:
The paper is a thought provoking treatment of one of the ways digital connectedness is reshaping society -- influencing the very physical structures that house it, but also the ways that we relate to the physical and social spaces of organizations and cities, and the ways they cause us to relate among ourselves.
Conduits for Caring
Nick Carr really challenges me to think because he sees things, well, politely, differently. So he puts "technologies of self" at the top of his innovation pyramid. And one way to see the likes of Facebook is as a podium for projecting self, and because we strive for authenticity, building "self" -- the image of self that pulls us into who we are ..becoming. So it is a platform for low-barrier-to-entry self-broadcast and a mirror in which we see ourselves -- in part as we would like others to see us, and so strive to become. Etc. At least that's my 2 minute hit on what "technologies of self" are about.
Yet Facebook and other social platforms aren't just about broadcast, they're about connecting. Which is somewhat about broadcasting, but also about transferring, moving information through circles of influence. And about moving caring. Humans connect, share stories, and develop empathy and caring. This is not about self. This is about community, about relationships and connections -- local and distributed, friendships and collegial relationships that form around shared interests, concerns, passions, quests for meaning in larger contexts than "self."
So is the pyramid upside-down? Does innovation serve the increasing scope of organism, going beyond individual to more interwoven networks of social interaction, ever pushing out the boundaries of the new social organisms so formed? We see this progression in mechanistic systems, and social systems, and socio-technical systems -- from simple to complex systems of increasingly diverse yet inter-dependent systems.
Whether than makes any sense of not, Carr's reference to Maslow's Hierarchy reminded me of this post: Leadership and The Brain.
Anyway, it seems to me that as innovation continues to reshape experience and advance what is possible, we cannot afford to lose caring. And caring is interpersonal and needs to be communicated. Otherwise it becomes a mechanistic network of information flows that simply serve the emergent technological organism ever driving innovation in the direction of more and more capable, sensing-responding, intelligence-supplied and intelligence-forming, machines.
We each have an ego bubble that is deflated easily by negative or simply flat responses to the work we pour passion into. Enthusiasm -- evident, communicated enthusiasm -- for what we do is important to maintaining a healthy ego bubble that buoys our spirits. Of course, we need a just enough ego bubble or our self-sense gets over-inflated and the loft is too much.
(The ego bubble concept comes courtesy of our 12 year old resident sage.)
Working to Refactor Your ... Memes
"Curation" has become a "thing" in this age where the amount of attention seeking has overwhelmed our ability to find and process right-fit material. I chanced on calling our scouts in netlandia "agents of Serendipity," so naturally I prefer that more poetic sounding appellation to the term we associate more with museums. I'm kidding -- "curation" also applies to art galleries and more, and is a really important initiative that draws attention to, and contextualizes, great work that would otherwise be hidden in the glut. :-) A superficial encounter with what I am doing in this Trace might cast it thus -- curatorial or Serendipity generating. But a deeper, more thoughtful encounter would hopefully produce the realization that what is going on here is a profound shaping of a 21st century philosophy -- the need for which arises with urgency from the crashing of the tectonic plates of social and technological evolution that is reforming the global humanscape...
And if you buy that, I'm also selling a bridge. To the future you. It is called a workshop. Software Architecture. But really it is one of those "refactor your wetware" sorts of things. But better. We do it with anticipation. And design using the cheapest medium that fits the demands of the extraodinary moment. When it comes to your wetware, you'd want to use the cheapest tools. No, no. I mean... I was just playing with the philosophy thing. That is a by-product of attending to the forces that are shaping the identity and value of architecting, and hence what capabilities we need to build.
Toyota's A3 Reports
Want me to show you how I relate this to Architecture Principles?
I was buoyed by very kind words on one of the Bredemeyer mailing list sign-ups that came in today. Since that is the other site I write, I like those encouragement "carrots" -- a lot. And I know, I know. I should use every jot of writing energy to write more useful stuff... This Trace is not consumable, nor commendable. But here I write as me. And I believe it is not just useful as a source of pointers to other work, but for the hard-wrought but vividly cast insights herein. Yes, yes, I know that if I want my work to be advocated I need to do work worth advocating. And this Trace is not it... (I get mixed messages though, because architects I admire keep returning to my Trace and that is encouraging. But say nothing. Which is discouraging. I mean, if there is nothing good to say, that can't be good, right?)
In our work in strategy and architecture, we highlight sustainability and view it multidimensionally -- not just in the environmental terms of biological ecology, but in terms of the social environment as well as the business ecosystem and technological environment. So, for example, matters like team flow factor. This orientation permeates our work, but here are a handful of places it has surfaced:
An architect needs to lead; in our leaning towards more flat organizations we still need to value leadership and expertise, and I think it is damaging to insist without reference to organizational context and system complexity that there is no merit to architect as distinct role. We advocate a highly participative architecture decision process, where members of the team fluidly and dynamically take on leadership for aspects of the system. But also follow. Well. And get out of the way when the situation doesn't call for that person to lead or follow. The architect as a role is simply to clearly vest system perspective and responsibility because, for more complex systems, this takes attention that delivery demands tend to supercede unless designed into the team structure and dynamics. To achieve sustainability and integrity, we need to:
That is, the architect role is there to serve the team, advocating and bringing experience to bear in designing for integrity and sustainability. Not doing so alone, but with the active and essential involvement of the team. Yet leading, and having the responsibility to make decisions when these may seem non-obvious from a here-and-now expediency standpoint but which are necessary for system integrity and sustainability. Not building everything for tomorrow today -- that's impossible! But ensuring that what is done today does not thoroughly undermine the future, especially when there are alternatives today that would enrich possibilities for the future rather than eliminate them. This takes vision, experience and leadership -- or, at least, where it takes experience, we ought to value that.
Anyway, I include team "flow" in social sustainability. A team that becomes mired in technical debt, for example, is in a situation where social and technical sustainability has been neglected. The technical integrity of the system has been compromised as a result of compromising the organizational integrity of the team. It can take strong leadership to counter the tendency -- with all good intentions and in the excitement of trying out new ideas -- to slip-slip-slip into mounting technical debt. Sure, the team can decide it is time to spend a cycle on refactoring. And for smaller systems the team can hold much of the system "in their head." The need for the architect role goes up, the higher the technical and organizational complexity of the system.
Habits of Word and Stance, Shape
Philip Hartman's post caught my eye. I agree with Philip that the quote is unfortunately gendered -- something that begins "an architect is" has the flavor of being definitional, and to have that followed by "a guy" draws a boundary. But I've seen worse -- one architect put it in terms of being the one who's male equipment is on the chopping block when things go wrong, which captures the responsibility aspect vividly but in a way that outframes women. Should we be so sensitive to these things? The language we fall into and are ok with doesn't just reflect our world view, but projects that view forward. We create reality, and use words to transmit the reality we see and hope to build. So words, one at a time, aren't important. But when massed, shape and transform. So saying, I also find myself becoming more sensitive with respect to my writing and also to the quote, to being more inclusive not just in a diversity sense, but in the full team sense -- all contribute to the architecture and its outcomes.
Uncle Bob and NoDB
Interesting colorful post. Uncle Bob drives a point hard. The counterpoint has to do with building on, raising the platform, ... which means accepting dependencies on a growing infrastructural base. So the technology choices that form the base are important. Moreover, they are "out there" so technologists feel they can talk about them without compromising what is "under the kimono." It's also what technologists are interested in -- the latest cool stuff and how it's being used to do more cool stuff. How it is used to tackle real tough challenges like scalability... by outsourcing key components of the challenge to EC2/AWS and so on... We deal with this in terms of separation of concerns, addressing distinct areas of concern with applicable views and an organizing model for architectural decisions.
The go to blog for who's doing what in the scalability space is Todd Hoff's High Scalability blog. I love the post on 20 Common Bottlenecks -- it is exquisitely introduced (referencing 20 story plots and stone soup -- beautiful, elegant, erudite, and yet utterly practical).
Right on the heels of the furor over Dell, a conference organizer commands women to "WALK THROUGH THE DOOR" (his capitalization). The lack of awareness, lack of curiosity about the dynamic, and willingness to think that all that is needed is for women to be called out is... part of the quality without a name. In this case an emergent property in the social system. And women have been feeling this emergent property and opting out. Opting out of technology mid-career. Opting out of entering the field. And opting out of conferences. Not because women are incompetent or timid or not interested in technology, but because there is an invisible "force-field" we're having a very hard time identifying, though it bubbles up as incidents and accidents of "sexism."
Lest you don't see the problem, please allow me to highlight: Only way? Stop hiding? Waiting for men to stop doing what they're doing? The feeling that the post left me with was that I was being shouted at to feel welcome. Which did the reverse. This is the person who sets the tenor for the conference. In a moment of irritation, he is willing to call out and shame women? Now a lot of women are responding very graciously, saying that indeed they shouldn't be afraid to talk, and John has a point. This is Janey's take on being the "straw" that triggered John's "open letter to women in tech." She has also responded very graciously on Twitter. Yet her post explains that she is very much not hiding being instead active in, and a generous builder of, local tech community, but feels she's not a good public speaker. [One has to wonder how much of that is society messaging her that she is not a good speaker because she isn't "authoritative" (in style, regardless of content) and "commanding" (because she has a woman's voice?).] Despite that input, John is still going with:
John characterizes this as being blunt. I know that he means well, but, bluntly, it is inaccurate and unfair. That John means well is a redeeming goodness. Unfortunately executed. But an opportunity to learn.
I do want to point out that it is not about being "over-sensitive" to one instance of digital "body language" conveyed through bold lettering and caps -- and condescending and confrontational phrasing. It is about the accretion over time that mounts to feeling shut out by an invisible barrier that sometimes erupts in a behavior that can be pointed to.
Each one of these instances can be put down as a "storm in a b-cup" where some get outraged and some get enraged and defensive. Instead, we should be "getting it" that the problem is systemic and it has its tendrils through many facets including the formative experiences of girls and boys and the ramifications through life of gender -- hormonal, social, genetic, whatever. So a better approach is to create dialog and awareness around the broader social issues of how to thrive as men and women together in this computing world where we leverage each others strengths and work with respect rather than making assumptions that belittle and deride. And it would help a lot to be welcoming and engaging rather than telling women to get over a problem that, the language implies, we created in our perception and imagination.
Here's a bit of context for those who are interested in raising their own awareness:
It is hard to talk about, because this field is so wonderful to work in. Indeed, it is so much more difficult to deal with because it is subtle. It bubbles up more observably in occasional incidents, for example where men feel ok appealing to men with images and jokes at the expense of women and so excluding women from the circle of camaraderie being established. But there is a constant subtle wash that erodes a woman's feeling of place in this field.
Men are more (mock?) confrontational, learn to spar and word-wrestle and so forth to establish camaraderie and social structuring. But women are socialized not to so engage, men (and women, but in a field where a woman is often the only woman in the room, any such observation is skewed by the population spread) do not welcome it coming from women, no doubt because women do not understand its inscrutable rules (I doubt men could articulate them). For the most part, this is wonderful male energy. I don't know the solution, but do think it ought to be one where we hallow and maintain what is wonderful and yet build a community that values women and makes us feel welcome and valued.
For decades we've been telling women to act like men -- to be assertive and "confident" and man up -- and yet not accepting it when women try that on. Of course the answer, equally, isn't to tell men to act like women. But somehow we need to get to the point where we recognize that there are different leadership styles and there are ways of conveying authority (in a mastery sense) without alpha dominance displays. Conferences are the gathering place of a community, and they set the tone for a field. The more alpha the tone, the harder it is for other styles to be tolerated. If the only way to diffuse the tone is to invite women (so demonstrating that their voice, their style, is valued), then take a little time to respectfully invite them. Believe me, women are never "just waiting" and "hiding" -- we're busy as all get out and a lot of what we are doing is enabling other people, buoying and boosting other people. So give back. Reinvest.
Disclaimer: The only event I have been invited to speak at was the CAEAP inaugural summit. They put it on vimeo and I link to that video for transparency, so people know what they are getting coming to a workshop with me. But that doesn't really do me justice, because workshops are much more we than me. When people work with me, they get a lot from the experience -- I've even been called "the man." A pinnacle in my experience, I can assure you. And I don't say that disingenuously.
5/22/12: And it's not just about women:
I explained to my son the other day that it is observable that we have a problem drawing women to this field, because that shows up in the gender distribution (and the huge drop since I entered the field). But what we have no numbers on, at least none that I've seen, is how many people we push away.
PS. I love that rjbs used Auden's poem -- which concludes thus:
It is such a short life! Why be mean?
5/23/12: This is Lego maker-shop is so cool: Lego for girls, this time hardware-hacker style. Go for it Lego!
Ahem. Missed Some
A useful collection (via Alex Matthews):
Well, except that Brian clearly missed some of the more important works, since he included not a single one of ours! ;-) Chuckle -- I imagine Gartner considers Cutter and Forrester competition. It will be nice when analysts and other "thought leaders" view their primary role as nurturing and growing the ecosystem, so that we can all do the right thing with respect to bringing useful material to the attention of the community.
The other day I passed on a pointer to kids drawings made into toys. Did it strike you how the shift from child's drawing to made toy changed how we respond to the drawing? It is now a design for a highly imaginative creature. As a design for so cool a toy, the drawing takes on authority it didn't have when it was just an inadequate rendering of something in "the real world."
How we see the pictures changes. So can't we shift how we see our own renderings?
This is a sequence of Sara's drawings. There I noted: "Even in terms of the code structure, we're creating abstractions that lend themselves to making the system more cognitively tractable." Which was a quite partial notion. We're also creating abstractions to render, to draw out from our mind's eye mechanisms -- weird and wacky wonderful software creatures we're inventively discover-designing.
(It was nice of Kris Coverdale to retweet my tweet. It is not an endorsement by any means, but when someone does an ack on a tweet there's at least a hint of resonance. I know I don't do that enough in situ -- I don't want to be too noisy on Twitter, so often I do the "ack" in this Trace. :-)
As for Bad Ideas...
Think ecosystem. Like this:
EA and EWITA
There's a fair amount of awareness raising in the Twitter-verse around the need to view enterprise architecture as whole enterprise architecture, and even extended enterprise architecture, rather than IT architecture at enterprise scope (or EWITA). But we need to be careful not to send the pendulum crashing over to Business Architecture as the holy grail, because digital/compute has become, and is becoming still more, woven into business capabilities and it really is important not to push technology (still further) off the strategy table. We have been working to bring design to strategy implementation through architecture, and to bring technology into strategic consideration because it is very much threaded into the business ecosystems we vest in and capture value from.
In strategy development, we have to be thinking even more (than just process automation and consolidation and integration) in terms enhancement of human capacity -- because waves of competitive disruption are relentless. And as we do so, we need to think about what we are doing to ensure that we don't just create an unsustainable situation where the rich get richer and ever more people are unprepared to compete with machines for jobs. Digital compute intelligence is on the march, and we ignore the capabilities we can built thereon at our peril. And we ignore the economic cost of destroying the consumer base at our peril too. Interwoven and complex. But we have to face these opportunities and the issues they raise -- as matters of strategy and of design. Oh, yes, such complexity is hard to design, but we need to get better at it -- experimenting, iterating, developing feedback loops, working fractally and again with feedback loops across the fractals, etc. etc. ETC. ;-)
IBM saw that they had a technology that would change the world, and is moving fast to fully exploit it -- growing Watson's product family tree.
Now, did Microsoft see Kinect as an equally world-reshaping technology? Has Microsoft imaginatively and aggressively pursued all manner of applications of Kinect -- in addition to treating Kinect as an open space where lots of innovators will take Kinect in valuable directions, helping to reveal to Microsoft opportunities it has not imagined? If it has, please point me to examples.
One of the hallmarks of a strategist is vision -- is being able to see where something can go. Seeing the possibility. And shaping the course to get there. Some great theater along the way helps. Steve Jobs knew that. IBM's Ferrucci knows that.
5/31/12: Ah, here's the answer:
And this is interesting::
6/4/12: Preston Gralla: Microsoft can innovate, but it falls short on capitalizing, Preston Gralla, June 4, 2012
The timing of innovations is important, and thinking in terms of ecosystems (Microsoft has done a good job of this in many areas -- ecosystem readiness, investing in the infrstructure of the ecosystem, developing ecosystem niches through product and solution families to expand the avenues for enrichment, etc.). And there's a "performance art" aspect to leadership...
Wow. Seriously. Wow.
12 employees! That's some awesome value creation!
Facebook has 3200 employees, and on the day of IPO ws valued at $104 billion. To be fair, Pinterest runs on AWS, so it has proxied its operations for the most part.
5/22/12: More in the category of Wow!:
What Happened to Middle Ground?
Seth Godin: Be judged. Or be ignored.
How about just being accepted? I know, I know, it sounds so "big happy family" but hey, maybe we could extend our caring networks along with our influence networks?
Yes, yes, once one is "out there," some folk will be harshly judgmental, take issue, look for the grey when you're creating a simplifying distinction to drive a point (all models are wrong, and all that).
But should the call to action be to show up anyway, since the alternative is to be ignored? Or should we acknowledge how much goodwill there is, how many people really are empathetic and kind and see the good in what others lay their ego and self-concept on the line to offer? And if we do incline to judge, perhaps our call to action should be to judge less quickly, less harshly and rather use the opportunity as a flexibility exercise, working on one's ability to see from another point of view? Should we accept the world as a harsh place, or seek to be the change we want to see in the world (hat tip to Gandhi)?
This is a key architectural insight. Continuous improvement efforts often accept the current structure, and look for improvement opportunities given that structure (and the dynamics it enables and constrains). To more dramatically improve flow (cut costs, improve value, cut time, etc.), we need to invest in new structures and structural mechanisms that enable flow and remove constraints.
Prompted by kind input, I realized that the last time I pushed anything across to my blog was 2 years ago! That just indicates how quiet that venue was -- neither I nor anyone else noticed it was dormant!! But it does have the usual conversational features, so I figure I'll try to be more disciplined about piping posts over there. Well, surely not all posts...? Which gets me back to the trap that tripped me up before... Which posts? So, I've begun by posting the Conceptual Architecture piece as a 3 part series. Maybe that will motivate me to do likewise for Meta or Logical? Or maybe it will open the flood gates from this Trace, pushing postlets from here to there? Maybe I'll move house, and entirely shift over to the blog format? Who knows? I've liked the freedom from inhibition of this Trace, but I'm open to liking the conversations of a blog. Assuming there were some... (and not just mountains of spam...)
And you will no doubt be pleased to note that I added links to (most) posts in the left sidebar (near the top). I haven't been keeping up on the post links, because no-one uses them... (All the stuff I should make automatic, but I have bigger system development concoctions to occupy those cycles.)
Well, anyway, I do get it that it is hard to "include" this Trace in conversations when it is hard to link to specific posts, and if it is hard to include, then people don't gradually come to know about it. Over the years I've been discouraged because over and over and over, even people who have emailed me that they loved a paper I've written, don't mention or reference it, so I just sort of got schooled by life that people don't really want to include me in conversations. But I'll try harder. :-)
Right on Cue
Daughter: "One day, when I'm about 24 years old, I'm going to have to figure how to get what I want without begging. Either that, or upgrade my begging. Likely the latter."
How the world works. ;-)
5/22/12: Life has a sense of humor, which is clear through its timing.
Oh, I'm playing with your notion that I'm begging. ;-) I don't want to be included because I mentioned it. I want to be included because it is the obvious thing to do. And so far, it hasn't been obvious. I don't think it is because my work isn't valuable. But it is... "different." (My husband and tweener daughter say I'm "cute" -- I think they mean "foolish, but in a good way.")
The same two people responded to my poll as have responded to my requests for feedback/perspective on this Trace before. I do so immensely value their goodwill towards me. A third responded indirectly, and I value that too of course. It's the indifferent silence that spooks me. People come back, so I guess not everyone is booing... but it's hard to know...
Well... no doubt you will (re)read my Conceptual Architecture: Why post (and yesterday's What post)... and have lots to criticize... crash my confidence... and all that... ;-) But... if you don't like:
I'm firing one of us! Probably me. 'Cos you're like valuable. To the world. And stuff.
Actually, I am going to fire myself. Because now I see that it should be: "and in these interactions effecting emergent properties."
Sigh. I hate blogging. I need to be able to edit and re-edit what I write. I think that continuous deployment is valuable, because it makes me more self-conscious/self-critical... but this ethic of publish and leave to stand the test of scrutiny and reaction is very damaging given my style and predilections...
Must, Must, Must See!
The latest RSA Animate video (just out today) is super stupendous awesome great amazing ... ok you get it...
Trees and hierarchies, ecosystems and webs or networks. Really front and center topical for this exploration I've hauled you along on!
In case my tweet got buried in the flow, it's here. Retweet at your own discretion. Hint: it's big. Your followers will thank you. :-)
Image source: RSA Animate – The Power of Networks
Rats! Now I want to add a "zones of organized complexity" bullet point to my Conceptual Architecture piece. ;-)
5/24/12: Nice post on fractals and Manuel Lima's talk here: The Power of Networks: Fractals of Complexity Brian Hoffstein on May 24, 2012.
I was astonished that a number of people had a "nothing new" reaction to the video, demonstrating the willingness to "no big deal" work that pulls together insights that are bubbling up in various fields and creating a new weaving that sheds fresh light and inspires new audiences to ah ha insights and deeper, more contextualized understanding. How much capacity we have for awe at wonderful accomplishment. Let's focus there.
System Features and Properties
This comment struck me:
These columns I wrote for the Bredemeyer site, relate:
And this from my Trace:
6/1/12: Economics of Software Quality, Steve Smith, 6/1/2012
6/3/12: Static Code Analysis, John-Carmack, 12/24/2011
Inclusive. Yeah! ...but does it mean the same thing to everyone?
The jury is still out, but it is a compelling idea, and momentum is massing and massing. Like this:
At the same time, we have a lot of "more of the same" going on, with major "land grab" consolidation in the food/corporate catering and health care industries in the US, for example. Now acquisitions and predatory expansionism doesn't necessarily rule out becoming a "connected company" or "social business," nor being intraprenerial and innovative. But driving out duplication and finding cost efficiencies through consolidation and automation tends to put the focus on operational efficiency and value extraction. The challenge then is to combine 21st century responsiveness through empowered and compute-enabled relationships leveraging co-creation and committed engagement with more 20th century notions of tighter synchrony and cost efficiencies through automation and streamlined flow.
If you're interested in the ecosystem thread (related to "connected" and "social", you might also like: Merchant Found Her Umbrage
Too busy to do much more than leverage. So, some magpie trinkets:
I like this as a way to frame meetings:
because then it is clear that meetings are about alignment and getting the co in co-create to happen with shared purpose or aligned intentionality. (Sounds like a good time to plug Sibbet/The Grove's graphical facilitation and Gray's Gamestorming, and model storming and such.)
On the Other Hand
I need to hasten to add that I do not mean to suggest that architects need to be familiar with or use all of these! Only to point to illustrative thinking-doing-presenting tools that are helpful within these bands of competency area. (And the illustrative examples may also help you grok the intent/meaning of the bands better.) I should also clarify that as the scope of one's responsibility increases (from application, to system(of systems), to business area, to enterprise, for example), the demands on organizational politics and leadership goes up. The "strategy" aspect also shifts, from product to greater business scope. We advocate that architects at application/product scope are (along with the full team, ultimately, but let's just focus on the architect here) responsible for right system built right, and that it's that first right that often comes as a surprise as many architects thought they just had the monkey on the built right part. (Or for "good, right and successful architecture" not just "good architecture.") At first, the architect may be conscribed to, at most, translating business strategy into technology strategy, but with demonstrated strategic savvy, greater empowerment of innovation teams, and so on, architects come also to have input into business strategy setting and active anticipative and responsive evolution thereof. Anyway, to earn a place in the strategy conversation, it is useful at any level of scope to use some of the customer context and ecosystem/competitive landscape understanding tools to be better informed and to be more adept at posing the capabilities technology brings to the table in strategic, value enhancing-capturing-sustaining terms.
Here are some more conceptual models (or tools for exploring, thinking, reasoning, analyzing, etc., or to organize and present, etc.) using the Bredemeyer Architect Competency Framework as an organizing model:
Well, as you can see, that is a work in progress... think continuous deployment... and remember the rationale is to get feedback and course correction earlier. So, what else? What's missing? What frameworks do you like and think I should add? Etc. I started the game, now you get a turn while I get back to some real work.
For more on the competency framework, see:
6/5/12: All Hail the Generalist, Vikram Mansharamani, June 4, 2012
Mentioning the architect competency framework reminds me of Vitruvius:
And, minds being associative, naturally led me to think again of Vetruvius' model of design integrity:
Looking for a reference on this "Vitruvian architectural design framework" (my impetuous appellation), this struck me as interesting (and relatable to systems architecture): The Vitruvian Virtues of Architecture: Utilitas, Firmitas, Venustas. I really like the 3 interlocking circles image for this! These qualities interact in a coherent system, and are interdependent, each relying on the others (there is no utilitas without firmitas, etc.).
The model covers fit to purpose, fit to context (cultural, environmental, across use contexts and allowing also for shifts in context in high change environments), and internal fit (integrity, durability and resilience) -- though these slice-and-dice differently than the Vetruvian model. Which is to say, one might want to map fit to purpose to utilitas, but I think venustas is also implicated in fit to purpose, if we think in larger, more meaning-full ("higher purpose") terms. Let this triad be known as the Ruffyan Virtues of System Architecture. ;-)
6/1/12: This podcast, via Doug Newdick, is a wonderful backgrounder on Vitruvius and his great work on architecture and the architect:
I especially like the points about the knowledge areas of the architect, around minute 17 (to 20). Further on (eg around minute 27) there is also some discussion of principles and patterns Vitruvius distilled. This discussion moves to Vitruvius' Catalog of Machines and how Vitruivius made the point "the architect is the mind behind it all and is in charge of using the machines in the right way." Again interesting points on the education of the architect around minute 37: "...depiction of the architect as a Renaissance man -- who is often at the service of a patron... so effective political role of the architect with respect to their patrons."
In the spirit of "follow Friday," I would like to applaud the following for "mutualism" and giving back to the field:
You can see from the short list that these must be remarkable men in a time that demands remarkable people to remake this digitally connected world into one that is inclusive and caring, where people "put more in that they take out," reinvesting in the vigor of the field rather than simply drawing value from it. Now I realize that generally speaking, follow suggestions are more noticed by the person being suggested than anyone else. But in this case, in a world that needs larger-than-life people of sensibility and smarts, these gentlemen evidently have those bases covered.
There are architects in client organizations that I can't mention by name, but they should feel thanked too!
Anyway. The list above are people who raise the platform of the field, elevating my, and a good many other people's, experience of it. Thank you gentlemen!
Yahoo Gets the Toilet Treatment
This article is generally quite good:
But really, what does the excrement and f-words add? Tech mojo? Um. Looking to monkeys as role models and exemplars in expressing disdain and objection? Like this: Monkeys throwing poo? It's actually a sign of INTELLIGENCE - especially if they score a hit, Bob Waugh, December 1, 2011. Aw. Just having fun with the parallels. :-)
That aside, it is a great heads-up to enterprise architects acting as counselors to strategic management on an acquisition spree.
Flickr: Not dead yet! Flickr is awesome. Still. We can be such gadflies chasing the new-new, and forget that we also have a role to play in ensuring that what we treasure has impetus to endure.
Mankind has done some awesomely inspiring things! Like this:
That is an incredibly beautiful monument!
I also write at:
- Bredemeyer Resources for Architects
- Accepting Good Enough (Must Read)
- Good Ideas (Sketching)
Strategy, Innovation, Ecosystems
Scanning Trends and Other
- Must See (Energy solutions)
Architects and Architecture
- Todd Hoff (highly recommended)
- Anna Liu
- JD Meier
Architect Professional Organizations
Agile and Lean
Agile and Testing
Other Software Thought Leaders
- CapGeminini's CTOblog
CTOs and CIOs
- Werner Vogels (Amazon)
- Jonathan Schwartz (Sun)
CEOs (Web 2.0)
- Don MacAskill (SmugMug)
- Wired's monkey_bites
Social Networking/Web 2.0+ Watch
- Dan Roam
- David Sibbet (The Grove)
Strategy, BI and Competitive Intelligence
- Freakonomics blog
Um... and these
- CNN Money Business of Green videos