The Space speaks! That's a wild thesis as it's
also expansive in our mere act of entertaining the concept. More to the point,
space possesses syntax as Space Syntax, the legacy of Bill Hillier.
I came across this interesting work (Space is the Machine, 1996) in
architectural theory while thinking about the analogs of natural construct of a
project graph based schedule, the so call bare project works precedence
diagram, basically a directed graph of project works. A project graph also
resembles a building architected by the project total flow of works. That all projects
ultimately will be realized in forms of a constructed facility (like a power
plant) or a product (an instance of materialized configuration of requirements
-to -performance) are all examples of a commensurate aspect of architecture:
there are architectures within this main architecture (software residing on a
controller system serving a special machinery). Hillier talks about
architecture as a space of externalized configurations on interior space, our
mental constructs of relations among other relations (his abstract but
intuitive definition of Configuration). We project our notions of space and its
inner relations into constructed buildings within environments. How would two
different engineered constructs like the Suez Canal (in news lately for its
human caused choking) and the San Francisco Gold Gate compare? The latter is
relatively modern (commissioned in 1937) whereas the Suez Canal has been an
elaborative and progressive causeway for more than 2000 years. Both of these
systems are communicating an idea of connectivity with their own variations and
specific internal relations, the aesthetic space of Golden Gate should
overwhelm Suez Canal...! Hillier's thesis in Space is the Machine (discussing
his Space Syntax) is also addressing the dual of syntax, the semantics in terms
of configuration. These are fine and the subject matter experts will debate. Hillier’s
thesis of configurational space or a theory of configuration of architecture is
very close to Von Foerster’s idea of eigenform. I wonder if Bill Hillier was
aware of this (second order) cybernetic concept? Ali
Simplicial Notes
Writing about an idea of connectivity…
Wednesday, April 7, 2021
Saturday, April 3, 2021
Communicating an idea that I have encountered
in practice: contracting theory.
Heinz von Foerster’s witty remarks are well quoted among his fans and
colleagues, I give the man (already departed) the credit. Please see his take
on the dual opposite role of soft and hard sciences.
The
hard sciences are successful because they deal with the soft problems; the soft
sciences are struggling because they deal with the hard problems.
In being awarded a prize to one or a few of its contenders (take Nobel Prize for instance), the eyes are on the newly awarded. Interestingly, there’s a Nobel Committee of the already winners (or Laureates) deciding the merits of awarding the prize to the next member of the family also dealing with the Nobel Committee rate of turnover (the rate of Laureates passing away)! Let's leave these aside.
Enter
contracting theory: In the context of contracting and agreeing on a contract we
arrive at the contract agreement, let’s say two parties A and B agree on a set
of clauses (rules, laws, codes, provisions, etc.). The two bodies having
entered in a contracting agreement are two separate bodies, organizationally
and business-wise speaking. In this sense, the instrument or medium of the
contract agreement is the obligatory binding element (which is very complex,
complex here is a many faceted simplex) bringing the two bodies together to
achieve what was required to be realized in the ways stated by the agreement.
In this review, I am taking a role as an observer from outside and purely and
conceptually appraising the formation (and deformation) of the contracted
parties.
The thesis:
the contract agreement carries its opposite within itself called expansive
disagreement.
This is not a playful take on the term contract
rather an indirect and structural viewing of the resisting bodies of both
parties A and B having been contracted into a unifying agreement. The parties
are functioning bodies and generally at ease as they are and as they persist in
their baseline business operations. This much is granted and is normal. What is
not granted is the tension area in and around and within the contract agreement 'space' which brings these two bodies together. The obligatory rules of the agreement
despite the name are actually intimating causing-effecting lines of force that
repels the two parties and at the same time pulls them back in within the
agreement because they chose to do so: we say that we signed on this contract
so we are obligated to fulfill the promises as agreed else there will be consequences.
This is the fear or business risks of what could go wrong that are at normal (or
perpendicular direction) to the direction of the contract realization. The
contracting agreement is trying to bring two bodies together that are foreign
to each other. At the same time, as the contract time goes on, each party
within the organization is used to its normal business practices while both
parties after having been contracted in by the Agreement mechanism, experience
tensions at the boundary of the contract. I call those contract interactions as
tension as pulling apart since the
two parties interact (for their performance) at the boundary of the contract as
two entities each trying to come as close as possible while in essence (the
organizational entity) they are separate and foreign to each other for what
they do and what they are used to. Worded differently, the two parties have
disparate operations which by the mechanism of the contract, each experiences
the reaction within its own organization, sometimes as ripples and sometimes as
shock waves. This way of viewing is tried and true: people who have managed
substantial contracts (let’s an engineering and construction contract) can attest
to the tensions at the contract periphery and as each party faces the other. This
analysis of a contract agreement as a dialectic object (two objects A and B
communicating with each other against a medium) may sound strange but it has a
very simple mechanical model with deep insights: the contract agreement is the
envelop of two rolling (non-rigid) bodies on each (rubber meets the road!)
producing local interface deformations called Hertzian stress, so the stress experienced by a manager of a
complex project trying to support the fulfillment of a contract agreement.
By Lord, this is so true!
Sunday, October 11, 2020
I came across Conway's law on 9/18/20. The note has a personal significance and not necessarily for a would be visitor of this post. I will state it anyway. What's the noteworthy about Conway's law? Let the author, Melvin Conway speak for himself:
Conway’s law stated in 1968 says: Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure.
I could not find any hint to this law (it's in my view a curious recurring fact and less of a law as laws are either ecumenical or subject to repeated empirical observations/testing.) in the PM BOK. Perhaps in future we could open up a small corner for Melvin this reference model of project management norms.
In his 1968 brief paper (here's a link) published in Datamation journal, Conway suggested a link, a map, or a bridge from the way people (in a design organization/department) communicate with each other to the way the product is actually put together. In a broad respect (in a wider view) this law says that if you see a design (a specification, a machine, etc.) it's an indication of the way of communication among its designers. The indication in Conway's words (and assessment) had a stronger (mathematical) requirement: that the communication across the design team was preserved in the structure of the configured design. We really need a mathematician (with enough insight into both design theory/practice and graph theory) to tell us if the technical term used by Conway does really hold, ie, the homomorphism. A homomorphism for visual depiction is like an arrow! It is a pointer from A to B which by so doing also induces a path and direction, 'from A to B'. I am not stating the graph theoretical notion of the homomorphism as it might scare away the non-mathematical reader.
Through practice and in my opinion, I am inclined to take sides with Conway and see enough of topical/historical/indicative evidence for his formulation. I see he had a fine and deep point about the bridging of two vastly (if not total separate) realms of sciences: the communication among people which is a social science topic, and the configuration of a design which subsumes a few disciplines under this name (system science, design theory, engineering design, and pattern theory). I love Conway's paper!
I began this post to suggest an extended version of his observation that there is a mirroring relationship between the design team collaboration and the performing design. I've been looking into this relationship for sometime. More on this later.
Now if there’s a direct relation between the
communication structure and the structure of the designed product of an organization,
could one look at this model the other way around and let's say design a communication structure that
could be copied in the designed product? It’s tempting to say yes, That's WWW! The communication on the Web
is based on the TCP/IP protocol. Jon Kleinberg depicts (Networks, Crowds,
Markets, 2010) the Web as a bow-tie structure with a strongly connect component.
As he says:
Taken as a whole, then, the bow-tie picture of the Web provides a high-level view of the Web’s structure, based on its reachability properties and how its strongly connected components fit together. (p. 391)
What about the (inter-nodes) communication structure, the TCP/IP. This is something that may not readily lend itself to such exercise. To be continued.
Ali
Wednesday, October 7, 2020
Back to the S curve: while we have great math
machinery to discuss the form and functional properties of the logistic
equation, despite my research, there’s no phenomenological explanation of why
the shape of the curve is as it is! The applied math literature discusses the application
of the equation to various cases and even literature review like the paper by the
late Dutch statistician, JS Cramer (2002), does not reveal the inner working of
the equation. If the equation applies to a wide array of population phenomena, it’s
puzzling to explain why we have three distinct phases of the growth phenomena:
the slow start, fast ramp, and the slow demise or end. To attribute the three
aspects to the form of the equation does not explain how come this behavior? I have
been working on a conceptual explanation of this behavior where the background
to this growth curve needs to be considered. In this sense, it is indeed the interaction
with the background to the foreground growth that modulates the overall form.
Ali