The brief cannot – or should not – exist in splendid isolation.
The relationships are not fixed, they’re knitted together in different ways across time so they’re strengthened by each other and able to hold themselves, to resist tension.– we look for the patterns that describe how design systems and processes work and we turn them into machine-readable logics and rules.
Algorithmic design.– we use different algorithms to suit different patterns, but we are cautious.Algorithmic processes can be complex and not easy to understand, so we look for moments of intervention within processes that allow people to interfere and hopefully understand the process.
(And we document everything!).– we don’t exist in a bubble, so we join our design automation tech to other systems and platforms so as not to duplicate functionality where it already exists, or ‘centralise’ either data or process.
– ultimately, technology is about people and we want to put design automation into the hands of the many.
The experience is not supposed to be deterministic but reflexive and co-created between people and technology.it does not account for the fact that making a larger number of repeat units itself leverages economies of scale and the unit price for small scale could well reduce over time.
This is the dream of new nuclear, where the aim is that smaller multiple units will deliver both a time and cost improvement..The conclusion for me is that scale absolutely matters and it needs to be carefully and thoroughly considered.
and modelled not just for one product but for the unpredictable portfolio of products that will come.the reality is that.
(Editor: Ultra Trackers)