A Trace in the Sand
by Ruth Malan
What's a Trace?
Hell if I know, any more. I thought it was worthwhile. But if no-one bothers to find it so, no-one bothers to say so. Well. It is depressing. At least.
I know. This is an unusual format. That it has been shown generous kindness is amazing!
From time to time, someone is extraordinarily kind. Moreover, attention takes time and the compliment it pays is the more sincere since it is a side-effect. I am grateful.
But. If I want an audience of more than 4 or 5 clearly exceptional people, I shall have to write for that audience. Hm.
Well, would you miss gems like this:
Isn't that worth the price of admission right there?! Okay, I know. The price is high. So many words.
Still, I guess my sense of humor is a little too... referential... for most people... ??? Many (possible, and possibly ambiguous) relationships under uncertainty, characterize complexity... So. It depends what is being named. You see? It's complicated. ;-)
So, does that mfeathers teaser decode to:
which may be visualized as:
Using the past to predict the future under conditions of growing entropy is... let's just say... hard? At least. Growing pressure to meet schedule predictions and attendant commitments increases entropy... Spiral.
It's for SCIENCE!
Will you please help me help my son get lab rats (that's you -- please) for his science research seminar project in high school. Thank you. Here you go..
Stunningly Humbling Week!
and a kind shout from Grady Booch! That mention was especially kind, given that Grady has a wonderful long-running column in IEEE Software (first on architecture and now on computing, especially as it relates to the human experience), and in the Sept/Oct edition he contributes to the "learn to code" discussion with a wonderful historical perspective, and observations about where we are at:
Of course, Grady, the SEI team and Philippe Kruchten, the Hofmeister, Nord and Soni team at Siemens, and Dana Bredemeyer and I. and our colleagues at the Software Initiative at HP, along with others, were doing field shaping work in architecture in the last millennium. We might hence be cast by the uninformed in BDUF caskets. However, those familiar with visual architecting know that we have taken a more agile than Agile approach since the mid-90's. Minimalist, just enough, participatory, messy and non-linear, evolutionary, these were all part of the orientation we advocated long before the Agile Manifesto. We, and others like Rebecca Wirfs-Brock, should be among those who leap to mind before the good Mr. Fowler when it comes to architecture in any context, Agile included. Martin Fowler is very good at packaging up what is at the cusp of a major "happening" in our field, but it is in the wake of pioneers who made that wave happen. Oops. Did that put a target on my back? I mean that with enormous respect, because it takes non-trivial insight into our field to be able to do that, and he does it superbly! Further, we're all learning from each other, so what Martin does is what we do.
11/25/14: Craig Jordan added another two posts to his series:
I can't see the third in the series. Can you? Not sure if it is LinkedIn behavior on my end...
Perlis on Style and Idiom in APL
Under the principle of facing realities (elephant in the room stuff), we went with "organizational politics" in the architect competency conceptual framework (rather than alternatives like organizational dynamics). And it falls in the general rubric of Organizational Effectiveness (in our updated model, featuring Strategic, Organizational and Technical Effectiveness as the three legs of the tippy stool of architect qualities and focal areas). Anyway, my eye fell on this in a trace from 2013, and I wanted to pull it out from under the pile of past words:
11/30/14: A "coder"? Hm. Well, I don't like stereotypes, or glib labels in danger of becoming stereotypes. Stereotypes are Procrustean frames -- they hack people down to the size of our (culturally absorbed) internal framing of them, rather than letting them be their full and unique selves. But we also have to get by with trying to communicate with less rather than more, and assume goodwilling in the writing, allowing goodwilling in the interpretation. By "coder," I was simply shorthanding those who, by the cast of how their organization (dis)empowers them, or their own preference and predilection for avoiding the messy social dynamics of working across organizational boundaries, focus on writing code. It can be hazardous writing in our field, because words are trip-wires for fury. But it isn't (always) clear which words, for which people. It is simply an organizational reality for many, that roles get cleaved and conscribed along communication and responsibility boundaries. We confuse many things, description and prescription among them. And we can choose not to perceive the smiles that convey exploration rather than didactic assertion, too. (Hint: that's a smile.)
Can We All Just Take a Moment
No, that was not an echo in that Ruffyan creature's tweet. Sheesh. It was taking a moment to appreciate someone who takes a moment to appreciate. A girl who represented her school in astronomy at the middle school state Science Olympiad, and who is vying to be on her high school's team, again focused on astronomy, among other things including projectiles. So, she was right thrilled at the history made today.
This Trace, and my exploration, is addressed at the challenges faced by architects -- of complex systems, in complex organizational situations. These traces should set the stage for talking about leadership in that context:
Yesterday I presciently tweeted a link to Cory Booker's talk on leadership. See my tweetsream for lots of great pointers from today, focused around Linda Rising's talk and the tweet-outs about, and responses to, it. The notion that leadership is something that happens throughout the organization, at different scopes and scales of impact, is not new to us. There is this from 2011: Playing Leap Frog
And this is from our Fractal and Emergent paper (2010), which you probably still need to get around to reading (smiles):
So, That was circa 2010 and I've learned a lot since. But it is still a leading set of ideas, no?
Oh. And I used the string image rather than my quip about the elephant. "If we put the architect behind the elephant, we may as well just give her a shovel because all she can do at that point is damage control..." I call it 'Getting Past "But".
Naturally we have been exploring leadership for as long as we have been working in this space -- Bredemeyer Consulting is 16 years old this month you guys!!! For example, there's "Leaders, Warts and All" from 2008 -- my kids, illustrating rapport, were so darned cute, weren't they?! Plotting against dad in the acorn wars -- I'm so glad I jotted that down; what memories it recalls to mind. Smiles.
Oh. And. The Paola Antonelli: Walk the walk talk is awesome. Rebels ftw.
Again, the focus above is on leadership and architects. Opportunities to create coherence and energizing import around doing something that can't be done alone, are all over; they are by no means limited to architecting. Obviously! But architecting is about getting things that need to happen from a broader, system outcomes perspective, to happen when they don't just happen on their own. The architect doesn't need to lead in every case -- shouldn't even. But the architect does need to lead when no-one else is, and there is no other way to accomplish the strategically significant system outcomes. Outcomes that are make or break have consequences. Quality of life and perhaps even jobs on the line for the team. Consequences -- maybe even safety or security-- for customers. And so on. Things that matter. A lot.
11/18/14: It is hard to talk about leadership, it seems. One wants to avoid implying leadership is strong on command and control, dictatorship and autocratic directorial styles that veer to the extreme in the dominance direction. But one also wants to reserve a place for decision making under urgency to move things forward. So it is not a uniform terrain. Sometimes charismatic and inspiring. Sometimes assertive and directorial -- just enough as fits the moment (at least, that's my preferred model of leadership, but I grant that there are other styles). Sometimes empowering, delegating, including, convening conversations, leading or enabling explorations that lead toward consensus. Stepping it up to making decisions unilaterally if time and lack of progress towards consensus means some decision must be made to move. Being aware, including self-aware. So decisions are revisited. Direction is set, and adjusted, and reset. As fits the moment, and the context, its forces, constraints, emergent outcomes and intents become more clear. And so on. Etc. Yadda. You get the picture. Books -- no shelves of books -- are written on this! :)
Also, conversations around partnering, collaboration, participation, and followership and facilitative leadership and so on, belong here too.
If you see me on Twitter, ridicule me mercilessly for giving in. I have way too much to do. As a bulletin board for pointing to people's work, Twitter does pretty well, but my "Serendipity feed" is overflowing as it is.
(Oh. Let's just take a moment to appreciate that someone gets my very dry sense of humor. I know, I know, it is so dry California should probably bar me from entry, lest I worsen their drought. Harhar? No, no. You know how it ends.)
(Yes, the last line is, among other things, a meta-comment on how twitter has become a medium not just for telling and selling, but also for meting social "normalizing" often with the big stick of social shaming... I do pack rather a lot into a line.... ;) Plus also To Don't lists, for those who missed that that is a thing. ;)
(What? If you'd known it meant all that, you'd have retweeted it too? ;)
11/27/14: "Plus also"?!? I know. I know. I flagrantly break the rules, so that when I do so by accident, you'll just assume it was"art." ;) Um, no. That's not it. I bend grammar. Tolerance workout much? Well, reading here is like, oh, the highest level of difficulty. :) It's really just training for the supergalactic levels of "translation" one has to become good at, being the parent of teens. Uh. No. Translating across all the different languages of the various stakeholders one has to not just make sense of, but sense to, architecting complex systems, with complex environmental inputs and impacts.
(via the ever awesome Dana Bredemeyer, who introduced it to me long back, but I re-remembered to trace-note it only now, in the context of the leadership discourse we're having single-mindedly; wink)
This, if we allow it, can lead our thoughts germanely and germinatively:
I don't mean to suggest heavy-handed governing, nor weighty governance (in organizations, around architecture). It is a way of thinking about minimalist architecture, and a wonderful statement and reminder of the great thinking we have to draw on.
Minimalist architecture? Dana's conception (minimalism and the arc of architecture), which I wrote up here (so credit Dana with the good ideas, and me for errors like using the word "asset"):
("long back".. re-remember... -- I know. I abuse grammar. Whaaaat? I don't get to break some grammar now and then? One has to take certain liberties, to bend words into the form of feelings and states. To open the conversation in a mind to include others in its comfy circle, informally exploring and trusting-non-judgmental... ;)
By Dana Bredemeyer
Oh, okay. Dana only took the photo, he didn't actually make the sun rise. ;)
A twitter-sized convo on design and delight, and this response:
reminded me of a trace from 2007, which I will reproduce here:
While Twitter does much to help ideas find mates, I do feel wistful about missing out on the social networking that really delved into ideas in longer-lived and respectful conversations. Like this.
Twitter is just so... flighty. :)
11/29/14: We have Paul Harland to thank for this:
Evidently I'm very in tune with the paradox of imperfection as foil for delight. This Trace? No? I'm stung.
Remind me to add a scan of Dana's photo of one of Antoine Bourdelle's sculptures of Beethoven -- it sparks, and so illustrates, delight at perfection in imperfection. Oh, my Trace is a poor imitation, to be sure. But still. Delight doesn't mean absolutely everything is perfect. Only that some essence hits a zing. :) What? My Trace doesn't? You're just odd then. No worries. You're in good company here. :)
I also write at:
- Bredemeyer Resources for Architects