上级分类: Ecosystemic Design科学与研究

原型系统

如何在现实世界中建立一个微系统?

YAML 问题

系统似乎是万物运行的方式。但是,如何运用系统思维进行创造性思考?如何创建一个微观系统?有什么通用的原则吗?


没有子分类。

投票 (可选) (别通知) (可选)
请,登录

用快速开发的语言(例如Python)编写概念证明。

然后,当您需要性能时,请使用更严格的语言(例如C)进行重写。如果需要,我怀疑您需要这样做。

Write proof of concept in a quick to develop language like Python.

Then when you need performance, rewrite in a more serious language like C. If you ever need to, I doubt you need to.


实际上,我正在研究更抽象的示例,以及如何使用思维模板来创建系统。

任何企业,任何社区,任何花园,任何系统都需要做什么工作(通过从自然系统的工作方式中汲取灵感)?

想一想,在系统中最重要的也许是能量的运动,而不是它的各个部分(如果是真实的系统,各个部分可能会发生变化。)

因此,对于作为系统运作的企业而言,资金的流动是关键。因此,必须设计一个交易时刻。然后缺少难题以启用该交易。

为了使花园作为系统正常工作,必须设计水和热量的流动。然后是花园里的植物。

对于要作为系统工作的社区或城镇,交互是必不可少的。因此,触发交互设计的空间。后来,有特定的人邀请了可能会来来往往的人。

Actually, I was looking into more abstract example and how to have a thinking template for creating systems.

What does any business, any community, any garden, any system need to work (by driving inspiration from how natural systems work)?

Thinking, perhaps what's the most important in the system is a movement of energy and not its parts (parts can change.. if it's a real world system).

So, for a business as a system to work, a movement of money is key. So a transaction moment must be designed. And then missing puzzles to enable that transaction.

For a garden as a system to work, a flow of water and heat must be designed. And later, the plants in the garden.

For a community or a town as a system to work, an interaction is a must-have. So, space that triggers interactions designed. And later, specific people invited who may come and go as they will.


//因此,如果我将这种思想应用于创建系统,那么我需要创建必备关系,因为它们构成了系统吗?那就是我的系统原型?

基于精益方法论,的确如此。这就是说,人们研究。与谁建立工作关系的那些人是谁?

//并且我怎么知道必须拥有哪些关系?

将社区视为一种​​产品,有点像想像一个鱼缸,是的,它需要哪种鱼?最终可能取决于我们想要生活在哪种鱼缸中。

// So, if I apply this thinking for creating a system, then I need to create must-have relationships because they make up a system? And that is my system prototype?

Based on the lean methodology, that would be indeed so. And that means, people-research. Who are those particular people to create relationships with for it to work.

// And how do i know which relationships are must haves?

Thinking of community as a product, is a bit like thinking of a fish tank, yeah, what kind of fish does it need? Probably will depend, ultimately, on what type of fish tank we want to have to live within.


在精益创业公司中,有一种称为MVP(最小可行产品)的方法,这意味着基于愿景创建必备功能,以便快速从现实世界中获取反馈。

因此,如果我将这种想法应用于创建系统,那么我需要创建必不可少的关系,因为它们构成了系统吗?那就是我的系统原型?

例如,鱼缸作为一个系统需要一条鱼,但也需要吃鱼便的细菌,以及需要吃鱼才能产生便便的植物!

现在,这如何适用于企业?

我怎么知道必须拥有哪些关系?

In lean startups there is an approach called MVP (minimum viable product) which means creating must-have features based on the vision in order to get feedback from the real world fast.

So, if I apply this thinking for creating a system, then I need to create must-have relationships because they make up a system? And that is my system prototype?

For example, a fish tank as a system needs a fish but also bacterias that eat fish poo, and plants that a fish eats to produce poo! Now, how does this apply to business?

And how do i know which relationships are must haves?


语言