how a characteristically swedish approach could deliver a different take on #complexproblems

so #it-#tech must come afterwards: it must come when the rest of us have designed the problem as robustly as we can without knowing if what we design is practical or not. only then will we not censor our ideas whilst we still have the capability to be ambitious and aspirational: only then will we only think of the real world.

mil williams, stockholm sweden, 16th april 2023

from my iphone’s notes app just now:

i’m open to being hired as employee or consultant or business. any of; any combination of. all too.

absolutely.

if it means i can stay in #sweden but not have to do it with the traditional kind of simplifying and incremental #tech ecosystem … well, then yes. even more so.

because i’m defo NOT looking for that if i stayed here. i’m not looking for it anywhere. wherever we took the #hq.

the #hq is a starting point but not an envelope of participation, anyway. we do live in a hybrid-working and effervescently connected world.

but i get the concerns, too.

now.

i still think best process would involve, first, an empathetic #consulting organisation; only after this, a single #tech corp (once the problem was scoped by us, i mean); and finally, an intimately connected #security complex and infrastructure, too … but always, in this field, independently managed by the country’s own existent domain experts. me only ever going so far as delivering a participation that consisted of being a consultant, ever.

if a #tech ecosystem of local and regional is preferred here, or anywhere else, it must be absolutely and heavily vetted to filter out those people and companies who won’t see/can’t see the virtues of the different architectures i am proposing. this we could do on the basis of historical behaviours and pronouncements; products and digital service rollouts over the years; and other data which could help us drill into company and individual cultural dna.

because i’m not prepared to accept intellectual and technological trojans into the projects and workstreams. and i recognise them easily enough these days, when i meet them. so no pulling any wool over my eyes on this. on other matters, maybe still. this, no longer.

i need to be firm in this. i really do. you will probably never understand why: but here i don’t budge. not any more.

and so this is why i’d prefer to scope with a #nontech ecosystem before going to #tech partners, in order to only then finally begin to implement.

so this is what i propose (though i am always open to evidenced counter-proposals):

1. a chosen #tech partner — a single organisation or a vetted ecosystem — can start by implementing already drawn-up specs, created outwith their thinking-spaces; just as liverpool did for me back in 2019, with almost fabulous effect.

2. only once they understand and embrace emotionally and intellectually the new #secrecypositive ideas, and the consequent #it implications, do they then start to have the right and duty to input at deeper and more conceptual scoping stages.

if you want to do a #consulting corp in #sweden for example, that’s obviously good and in line with my existing ideas.

or any #swedish entity in any endeavour which is not #it, of course …

yup. this as well. (engineering and most manufacturing and retail are now #tech too, but not #it-#tech for example).

so #it-#tech must come afterwards: it must come when the rest of us have designed the problem as robustly as we can without knowing if what we design is practical or not. only then will we not censor our ideas whilst we still have the capability to be ambitious and aspirational: only then will we only think of the real world.

• first we design the problem. always. the real problem

• it’s NOT NOT NOT going to slide into being “how to get paid soonest”

• it’s going to be how to reverse climate change. that’s the first #nontrad #security #complexproblem i want to deal with. that’s what will be my day-to-day. and i want citizens who don’t know what’s impossible to achieve to be scoping the envelope of the necessary over the possible

and that’s then when #tech comes in and starts to implement. and once it sees our new #neurodiverse #software and #hardware architectures work in practice is when it will also get freely enthusiastic about a totally different panorama from the #neurotypical #it they so firmly and universally believe in atm.

and so that’s when — but only then! — they’ll also be able to deliver #neurodiverse principles in their praxis. equally deeply as we will show ourselves capable of delivering in problem design. and so then, equally convincingly.

without reluctance any more.

without back-pedalling at all.

without thinking the problem needs to be reduced stealthily to how to get paid above and beyond how to save the species.

mil williams, stockholm sweden, 16th april 2023

Leave a comment