<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Keita SUZUKI on Medium]]></title>
        <description><![CDATA[Stories by Keita SUZUKI on Medium]]></description>
        <link>https://medium.com/@keita_72726?source=rss-b54030f2935c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VUgG0MKG5isj3M827y3A5g@2x.jpeg</url>
            <title>Stories by Keita SUZUKI on Medium</title>
            <link>https://medium.com/@keita_72726?source=rss-b54030f2935c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:26:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@keita_72726/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Multilayered and Multidimensional Thinking in Development: Chapter 9]]></title>
            <link>https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-9-95fd3232b750?source=rss-b54030f2935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/95fd3232b750</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[cognitive-science]]></category>
            <category><![CDATA[medical-devices]]></category>
            <dc:creator><![CDATA[Keita SUZUKI]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:01:04 GMT</pubDate>
            <atom:updated>2026-11-17T14:01:04.369Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Underlying Nature of Problems and Their Solutions Evolve Together</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*6dZM2VcMUorKlHl-MbiudA@2x.jpeg" /></figure><p>In the previous chapter, I considered how thinking about the ideal form and identifying previously unrecognized value are related. This chapter examines the relationship between understanding the underlying nature of a problem and considering how that problem might be solved.</p><p>In product development, one approach is to define a problem, analyze its causes, and then consider possible solutions. Identifying the problem, determining its causes, and evaluating appropriate measures are important parts of solving practical problems.</p><p>However, the thinking involved in designing something new does not necessarily follow this sequence.</p><p>What does it actually mean to understand a problem?</p><p>Consider, for example, endoscopic forceps, an instrument used during endoscopic procedures. The operator moves a control handle to open and close the forceps jaws at the distal tip through a wire or similar mechanism, allowing tissue or other objects to be grasped.</p><p>Suppose that, even when force is applied to the control handle, the jaws at the tip cannot generate sufficient grasping force. One possible interpretation would be that the problem lies in how effectively the operating force is transmitted from the handle to the tip.</p><p>However, the observed phenomenon of insufficient grasping force is different from the interpretation that the cause lies in force transmission. The possible solutions also depend on how the cause is understood.</p><p>For example, excessive friction may occur between the wire that transmits the operating force and the components surrounding it. The transmission of force may also be affected when the instrument is used in a curved configuration.</p><p>Alternatively, even if the operating force reaches the distal end, the mechanical relationships within the tip mechanism may prevent the jaws from generating the required grasping force.</p><p>If friction along the force transmission path is the main cause, it may be possible to consider materials or structures that reduce friction. If the cause lies in the distal mechanism, however, modifying its mechanical structure might produce the required grasping force without changing the force transmission path.</p><p>Although the observed phenomenon remains the same, the components that need to be modified and the possible solutions differ depending on how the cause is understood.</p><p>Of course, considering a possible cause is not the same as confirming that it is the actual cause. Several factors may be involved, and without sufficient information, the possible causes and solutions must remain hypotheses.</p><p>Another important point is that recognizing a possible solution can change how the problem itself is understood.</p><p>In the forceps example, the initial focus was on improving the transmission of force from the control handle to the tip. However, if modifying the distal mechanism could generate the required grasping force from the same input force, improving force transmission efficiency would no longer be the only possible solution.</p><p>It may also be possible to achieve the necessary grasping function through an entirely different structure or operating principle.</p><p>In that case, the initial problem of transmitting sufficient operating force to the tip can be reconsidered as a problem defined by the existing structure.</p><p>If the underlying objective is to grasp the target reliably under the necessary conditions using the distal jaws, another question becomes possible: Is it necessary to use the existing force transmission method or distal mechanism to achieve that objective?</p><p>What changes here is not the observed phenomenon. If the forceps cannot generate sufficient grasping force at the tip, that problem still exists.</p><p>What changes is the understanding of how the phenomenon should be interpreted as a problem and what needs to be modified to resolve it. Recognizing possibilities for different structures or functions allows the original problem to be reconsidered in relation to a broader purpose and set of conditions.</p><p>This brings us to the underlying nature of a problem.</p><p>Understanding the underlying nature of a problem is sometimes associated with investigating an observed phenomenon and identifying its root cause.</p><p>Understanding the cause is certainly important. However, from the perspective of developing something new, identifying why a phenomenon occurs does not necessarily establish what should ultimately be achieved.</p><p>For example, even if the cause of insufficient grasping force in the existing forceps were understood precisely, it would still be necessary to consider why that grasping force is required in the first place.</p><p>Is the objective to increase the grasping force generated at the tip? Or is it to grasp the target reliably? And beyond that, what is the grasping operation intended to accomplish?</p><p>The answers to these questions may change what is recognized as the problem that needs to be solved.</p><p>Here, the underlying nature of a problem refers not only to the cause of an observed phenomenon, but also to what prevents the underlying objective from being achieved and which relationships need to be changed to overcome that difficulty.</p><p>Understanding the problem therefore requires considering the observed phenomenon and its possible causes together with the intended objective, the existing structure, the conditions of use, and the relationships among them.</p><p>For example, if the current forceps structure is retained, reducing losses along the force transmission path may be an appropriate solution. If the distal mechanism itself can be modified, however, it may be possible to achieve the required grasping function through a method other than improving force transmission efficiency.</p><p>These two approaches involve different components and different conditions. Considering each possibility may also change the understanding of what needs to be resolved in the problem as originally defined.</p><p>However, the possibility of modifying the distal mechanism does not make improvements to the existing mechanism unnecessary. Each approach has its own feasibility conditions and constraints, and each must be examined to determine whether it can satisfy the required functions and performance.</p><p>Furthermore, different structures or operating principles may be alternative ways of solving the same problem. Having several possible solutions does not necessarily mean that there are several distinct problems to solve.</p><p>On the other hand, considering a particular solution may reveal other problems that had not previously been recognized.</p><p>Suppose, for example, that the distal mechanism is modified to increase the grasping force available at the tip. An endoscope has an internal passage called a forceps channel, through which instruments such as forceps can be inserted and advanced out of its distal end. If modifying the distal mechanism increases its outer diameter, it becomes necessary to consider whether the instrument can still pass through this channel.</p><p>Similarly, modifying the wire or surrounding components to improve force transmission efficiency may affect the instrument’s flexibility, durability, or manufacturing methods.</p><p>The possibility of solving the original problem is therefore connected to the conditions required for the proposed solution to be feasible, as well as to other problems that the modification might introduce.</p><p>For example, even if modifying the distal mechanism could increase grasping force, the resulting structure would be difficult to adopt as designed if it could no longer pass through the forceps channel. Reducing its outer diameter might then affect the mechanical relationships that generate grasping force.</p><p>Considering a structure intended to solve one problem therefore also involves considering the conditions necessary for that structure to work and its effects on other functions. Those conditions may change both the range of possible solutions and our understanding of what needs to be treated as a problem.</p><p>The important point is that this does not necessarily involve solving the first problem and then searching for the next problem in sequence.</p><p>Within a multilayered and multidimensional cognitive structure, considering a possible design also involves perceiving the functions it could achieve, the required materials and geometry, mechanical conditions, manufacturability, and usability as interconnected elements.</p><p>Recognizing a possible solution and recognizing the problems or constraints associated with that solution are therefore not necessarily separate events in time.</p><p>Furthermore, considering a particular problem or constraint may reveal solutions that differ from the structure initially envisioned. Those alternatives may, in turn, make other conditions and possibilities apparent.</p><p>As understanding of the elements and causal relationships that constitute a problem develops, it becomes possible to recognize which relationships could be changed to solve it. At the same time, considering the structures and functions that might become possible through those changes can alter the understanding of what should be regarded as the problem.</p><p>This way of thinking is related to the concept of the “co-evolution of problems and solutions” discussed in design research.</p><p>The co-evolution of problems and solutions describes a perspective in which a problem is not necessarily fixed at the outset and followed by a search for its solution. Instead, understanding of the problem changes while possible solutions are explored, and both the problem and the solution develop in relation to one another.</p><p>For example, gaining a new understanding of a problem may reveal solutions that had not previously been considered. Conversely, considering a particular solution may expose conditions or possible problems that were not initially recognized.</p><p>The concept of problem-solution co-evolution provides a useful perspective for understanding these reciprocal relationships.</p><p>However, the fact that problems and solutions evolve together must be distinguished from how those changes are actually perceived during thinking.</p><p>When analyzing a design process, it is possible to separate considerations of the problem from considerations of possible solutions and explain how each developed. Yet being able to distinguish them for explanatory purposes does not establish that they occur as independent processes within cognition.</p><p>In the multilayered and multidimensional cognitive structure described in this series, understanding a problem and generating possible solutions are regarded as different aspects of the same interconnected structure.</p><p>For example, when considering a particular design, the materials, geometry, and mechanical conditions required for it to function are connected to the intended function. Through these relationships, both the feasibility of the structure and the problems associated with it can be recognized.</p><p>Understanding the cause of a problem, considering a structure that could resolve it, and evaluating whether that structure satisfies the necessary conditions can be described separately. In the experience of thinking described here, however, these aspects proceed simultaneously, influencing and changing one another.</p><p>This subjective experience of simultaneous recognition does not establish that information processing in the brain is entirely parallel. What is being described here is how problems and possible solutions are perceived as related when considering a design.</p><p>Furthermore, saying that problems and solutions change in relation to one another does not mean that all information about a problem changes.</p><p>For example, suppose it has been confirmed that a particular pair of forceps cannot generate the necessary grasping force at the distal jaws, even when force is applied to the control handle. Recognizing that an alternative structure might achieve the required grasping function does not change the fact that the existing instrument fails to generate sufficient grasping force.</p><p>What changes is the understanding of how that phenomenon should be interpreted as a problem and what methods might achieve the intended objective.</p><p>Nor can the underlying objective or the conditions essential to achieving it be changed arbitrarily.</p><p>On the other hand, if a condition previously considered necessary actually arises from the current structure or operating method, an alternative means of achieving the objective may make it possible to change that condition.</p><p>In such cases, the understanding of what constitutes the problem and the understanding of which conditions can be changed are also related.</p><p>However, recognizing that a condition might be changed is different from establishing that the change is feasible. Even if an alternative method appears capable of achieving the intended objective, it is necessary to verify whether it is technically feasible, whether it satisfies the required functions and performance, and whether it actually resolves the problem under the intended conditions of use.</p><p>Likewise, a deeper understanding of a problem does not necessarily reveal all of its causes. If sufficient information is unavailable, several possible causes and solutions may need to remain under consideration.</p><p>A change in understanding therefore does not mean that the underlying nature of the problem has been conclusively established. Even when new information or possible solutions change how the problem is interpreted, it remains necessary to distinguish confirmed facts from hypotheses within that revised interpretation.</p><p>From this perspective, understanding the underlying nature of a problem is not simply a preliminary step before considering solutions.</p><p>The elements and causal relationships that constitute a problem, the objectives to be achieved, and the possibilities for functions and structures are interconnected within a multilayered and multidimensional cognitive structure. As the understanding of one relationship changes, both the interpretation of the problem and the possibilities for solving it may change together.</p><p>A deeper understanding of a problem can reveal possible solutions. Conversely, recognizing a possible solution can change the understanding of what needs to be solved.</p><p>The underlying nature of a problem and its possible solutions are therefore not treated as independently determined in advance. They are understood as changing through their reciprocal relationships within the same cognitive structure.</p><p>Within this kind of thinking, how can we distinguish between conditions that can be changed and those that must be preserved?</p><p>How can we distinguish conditions regarded as necessary because of existing structures or technologies from those that are essential to achieving the underlying objective?</p><p>In the next chapter, I will examine essential constraints and assumptions that can be changed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95fd3232b750" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-9-95fd3232b750">Multilayered and Multidimensional Thinking in Development: Chapter 9</a> was originally published in <a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic">Human–AI Coexistence : Principles for a Symbiotic Future</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multilayered and Multidimensional Thinking in Development: Chapter 8]]></title>
            <link>https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-8-6746a9f4a37f?source=rss-b54030f2935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6746a9f4a37f</guid>
            <category><![CDATA[cognitive-science]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[medical-devices]]></category>
            <dc:creator><![CDATA[Keita SUZUKI]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 14:01:03 GMT</pubDate>
            <atom:updated>2026-11-16T14:01:03.533Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Ideal Form and Previously Unrecognized Value</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*6dZM2VcMUorKlHl-MbiudA@2x.jpeg" /></figure><p>In the previous chapter, I considered how observing actual conditions of use can reveal problems that users themselves have not yet recognized, along with possibilities for improvement. This time, I would like to examine what should ultimately be achieved when such problems and possibilities become apparent, and how value that has not previously been recognized can be identified.</p><p>In product development, improvements are often considered in response to requirements for existing products or problems identified through observation of actual use. Improving insufficient performance or modifying parts of a device that are difficult to operate are important aspects of development.</p><p>However, when improvements are considered within the assumptions of existing devices and operating methods, the question of whether those assumptions are appropriate may not receive sufficient attention.</p><p>For example, suppose an existing device requires several operations to achieve a particular function. Simplifying those operations or reducing the force required to perform them would be one possible direction for improvement.</p><p>But are those operations actually necessary in the first place?</p><p>If they are required because of the current device’s structure, a different structure might eliminate the need for them. Similarly, if the same objective can be achieved through another principle or method, it may no longer be necessary to follow the existing operating procedure.</p><p>There is an important difference between asking how an existing operation can be improved and asking whether that operation is necessary at all.</p><p>The first question takes the current device and operating method as its starting point and considers what can be changed within them. The second examines what the device or operation is intended to achieve and reconsideres the method used to accomplish that purpose.</p><p>Of course, some existing operations are essential for achieving required functions or ensuring safety. Considering a different structure or method does not mean that every operation can be eliminated.</p><p>What matters is distinguishing between what is necessary under the current device or procedure and what is necessary to achieve the underlying objective.</p><p>Here, the ideal form refers to the state that should be achieved based on the intended purpose and the conditions that must be satisfied, rather than an improved version of the existing product or operating method.</p><p>For a medical device, this means considering why the device is used, what needs to be achieved for the patient, and what functions and performance are required to accomplish that purpose.</p><p>From there, it becomes possible to examine whether the existing structure or clinical procedure is truly necessary. Understanding which functions and performance characteristics must be preserved, and which could be achieved through different methods, may change the range of design possibilities.</p><p>However, considering the ideal form does not mean imagining an idealized state without regard for practical conditions.</p><p>In medical devices, patient safety and clinical effectiveness are among the essential conditions for achieving the intended purpose. Required functions and performance may also differ depending on the user, operating environment, and patient’s condition.</p><p>It is therefore important to understand what needs to be achieved and which conditions must be satisfied. The characteristics of existing devices and procedures also need to be examined to distinguish those necessary for achieving the intended purpose from those arising from the current method of implementation.</p><p>Returning to the earlier example, even if a particular operation is necessary because of the current device’s structure, the operation itself may not be the underlying objective. If another structure can achieve the same function, a method that does not require that operation may become possible.</p><p>If that alternative also reduces the burden associated with operating the device, it may provide an improvement that was not possible with the conventional method.</p><p>However, the ability to reduce the number of operations does not, by itself, establish that the new structure is superior. Other operations may become more complicated, or essential functions and safety may be affected. It is therefore necessary to understand how the modification changes the related conditions.</p><p>From this perspective, identifying the ideal form requires an understanding of the conditions that make existing devices and procedures work, together with consideration of which of those conditions are fundamentally necessary.</p><p>This leads to another question: could there be value that is difficult to recognize precisely because existing methods are taken for granted?</p><p>When users are familiar with existing devices and procedures, it is relatively easy for them to consider what those methods can achieve and what improvements might be obtained by modifying them.</p><p>On the other hand, if they have never experienced an alternative method, it may be difficult to imagine specifically what would change if that method were available.</p><p>For example, if performing a particular operation is considered a normal part of using a device, simplifying that operation may be expressed as an improvement request. Yet eliminating the operation altogether may never have been considered.</p><p>In such a situation, users may not yet recognize the value that could be obtained by eliminating the operation. Even if they have no significant dissatisfaction with the current method, an alternative that reduces their burden or enables another function may offer value they had not previously considered.</p><p>However, previously unrecognized value does not necessarily mean value that did not previously exist.</p><p>For example, reducing the burden associated with an existing operating method or achieving the same objective more appropriately may always have been valuable. Nevertheless, the means of realizing that value may have been unknown, or the possibility of improvement may not have been recognized.</p><p>Alternatively, new technologies or structures may make functions or operating methods possible that had not previously been considered, revealing potential value that had not been anticipated.</p><p>In the first case, a different way of solving an existing problem becomes conceivable. In the second, new technology expands what can be achieved, making it possible to recognize new objectives and potential value.</p><p>Both may lead to the discovery of previously unrecognized value. However, solving an existing problem and becoming able to consider different value through new functions are distinct developments.</p><p>Knowledge and experience of technology are also important when considering these possibilities.</p><p>Examining only existing devices and procedures may not reveal what could be achieved through different methods. However, knowledge of materials, structures, physical phenomena, and technologies from other fields can make it possible to consider alternative ways of achieving the same objective.</p><p>Learning about new technologies may also reveal possibilities for structures that were previously considered difficult to realize.</p><p>For example, suppose a function that traditionally requires several operations could potentially be achieved through a different structure made possible by a new technology.</p><p>If that structure could reduce the number of necessary operations, it might change the operational burden or the time required. A different operating method might also create possibilities for use under conditions to which the conventional approach could not readily be applied.</p><p>In this case, the new technology changes more than the assessment of whether a structure is feasible. As our understanding of what the structure could achieve changes, different possibilities may also become apparent for the objective originally being considered.</p><p>However, these remain possibilities predicted from the new technology. Being able to realize a new structure is different from obtaining the expected effects from that structure. Even if those effects are achieved, it is still necessary to consider whether they allow the underlying objective to be accomplished more appropriately.</p><p>Nevertheless, if new technology changes the functions and structures that can be realized, it may also change the range of possibilities we can consider as the ideal form.</p><p>This involves both understanding the objective through existing devices and procedures and considering new functions and structures in relation to that objective.</p><p>Understanding actual conditions of use can reveal what problems exist and what needs to be achieved. At the same time, considering alternative structures and technologies may change how we understand operations and conditions that were previously considered necessary.</p><p>The point is not to reject existing devices or procedures. By understanding what the current method achieves and the conditions that make it work, it becomes possible to consider what could be changed to create other possibilities.</p><p>The ideal form also does not necessarily have a single answer.</p><p>Even for the same medical device, the required conditions may differ depending on its intended purpose, the patient’s condition, or the operating methods used by healthcare professionals. A method that is appropriate under one set of conditions may need to be different under another.</p><p>Furthermore, if several methods can achieve the same objective, what each method can accomplish and the conditions it must satisfy may also differ.</p><p>When considering the ideal form, it is therefore more important to understand what needs to be achieved and under what conditions the objective should be accomplished than to decide on a single ideal structure that differs from the existing device.</p><p>This consideration also extends beyond the people who directly operate the device to others affected by its use.</p><p>In medical device development, it is necessary to consider not only the usability and workload of healthcare professionals but also patient safety, patient burden, and the effectiveness of diagnosis and treatment.</p><p>For example, even if simplifying the operation of a device could reduce the burden on healthcare professionals, the effects of that modification on patients need to be considered separately.</p><p>Conversely, even if the operating method remains largely unchanged, a modification to the device’s structure may provide other improvements in diagnosis or treatment, potentially creating value in those areas.</p><p>What constitutes value therefore depends on whom it concerns and the purpose it serves. These different forms of value are not necessarily independent, and a single change in structure or function may affect several groups in different ways.</p><p>It is therefore important to consider what needs to be achieved within the overall context in which a device is used, rather than focusing solely on satisfying the requirements of one user.</p><p>However, even if a designer identifies a possibility for new value, users may not immediately recognize that value themselves.</p><p>When conventional methods are taken for granted, it can be difficult to understand from a verbal explanation alone what would change with a different approach. In particular, users may struggle to imagine the specific differences that would result from functions or operating methods they have never experienced.</p><p>At the same time, a user’s failure to recognize the value of a particular method is a separate question from whether that method actually provides value.</p><p>A structure that a designer considers superior may fail to produce the expected effects under actual operating conditions. Alternatively, unforeseen burdens or constraints may mean that it does not offer sufficient improvement for the user.</p><p>It is therefore necessary to distinguish among value that has not been recognized, functions or structures that have not yet been technically realized, and effects that have not yet been verified.</p><p>Unrecognized value refers to a situation in which users do not understand the value or have not become aware of its possibility. However, that alone does not establish whether the value actually exists.</p><p>Similarly, something that has not been technically realized is a function or structure that has not yet been established as a working product. Even if a possible method of implementation has been identified, it remains necessary to determine whether the required conditions can be satisfied.</p><p>And even when a structure is technically feasible, further verification is needed to determine whether the anticipated effects are actually obtained. In medical device development, it is particularly important to establish appropriate evidence for the expected clinical benefits and safety.</p><p>Identifying previously unrecognized value therefore does not mean that the value has already been demonstrated. Recognizing the possibility of new value must be distinguished from actually realizing and verifying that value.</p><p>As considered throughout this chapter, thinking about the ideal form and identifying previously unrecognized value are closely related.</p><p>Understanding what existing devices and procedures are intended to achieve makes it possible to consider other methods that do not depend on the conventional approach. Considering what would change through those alternative methods may then reveal possibilities for value that had not previously been recognized.</p><p>Conversely, recognizing a possibility for new value may change our understanding of what should be achieved in the first place.</p><p>This does not mean that the ideal form is first determined and value is then sought through a separate procedure.</p><p>Within a multilayered and multidimensional cognitive structure, our understanding of current operating conditions and problems, the objectives we seek to achieve, possible functions and structures, and the value they might provide are all interconnected.</p><p>Recognizing that a particular function may be achievable can change how operations or constraints previously taken for granted are understood. Likewise, a change in how the problem is understood may reveal possibilities for different functions or structures.</p><p>Through these relationships, it becomes possible to consider not only improvements based on existing products and operating methods but also new structures and technologies that might realize value that has not yet been recognized.</p><p>When our understanding of a problem changes, how do the methods available for solving it change?</p><p>And could recognizing the possibility of a new solution also change the meaning of the problem as it was originally understood?</p><p>In the next chapter, I will examine how the underlying nature of a problem and its possible solutions are related and change within the same cognitive structure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6746a9f4a37f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-8-6746a9f4a37f">Multilayered and Multidimensional Thinking in Development: Chapter 8</a> was originally published in <a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic">Human–AI Coexistence : Principles for a Symbiotic Future</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multilayered and Multidimensional Thinking in Development: Chapter 7]]></title>
            <link>https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-7-6301386e7d7c?source=rss-b54030f2935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6301386e7d7c</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[medical-devices]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[cognitive-science]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Keita SUZUKI]]></dc:creator>
            <pubDate>Sun, 15 Nov 2026 14:01:02 GMT</pubDate>
            <atom:updated>2026-11-15T14:01:02.704Z</atom:updated>
            <content:encoded><![CDATA[<h4>Identifying Latent Needs</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*6dZM2VcMUorKlHl-MbiudA@2x.jpeg" /></figure><p>In the previous chapter, I considered the importance of understanding not only the requirements expressed by customers, but also the circumstances that gave rise to those requirements and the underlying objectives they are intended to achieve. However, problems that customers themselves have not recognized are not necessarily expressed as requirements. This time, I would like to examine how observing actual conditions of use can help identify such latent needs.</p><p>People who use a product have various kinds of experience with its functions, operating methods, and conditions of use. Based on that experience, they understand how to use the existing product to achieve their objectives.</p><p>However, being familiar with a product or a particular method of using it does not necessarily mean that it is the most appropriate approach.</p><p>For example, even if completing an operation requires several separate actions, users may perform them without questioning the process if that method has been followed for many years. Similarly, an operation may involve considerable effort, but users who have never experienced a way to avoid that effort may not recognize it as something that could be improved.</p><p>Under such circumstances, asking users what they would like to improve may not reveal the underlying problems. If they do not regard a particular action or burden as a problem, they may have no reason to express it as an improvement request.</p><p>However, it is important to distinguish between a problem that has not been expressed as a requirement and one that the user has not recognized. Users may be aware of a problem but have had no opportunity to explain it, or they may have given priority to other issues.</p><p>The latent needs considered here are those that have not been expressed as requirements because users have not yet recognized certain circumstances as problems or have not clearly identified the possibility of improving them.</p><p>Identifying such needs requires an understanding of what users actually do, as well as what they explicitly request. Observing how a product is used in practice provides an important source of information for this purpose.</p><p>In medical device development, it is possible to observe clinical practice and examine how healthcare professionals, including physicians, nurses, and clinical laboratory technologists, use medical devices.</p><p>What matters in these observations is more than the movement of the device itself. During what clinical procedure is it used, and what is the operator trying to achieve? What happens before and after the operation, and under what conditions is the user working? These circumstances also provide important information for understanding how the device is used.</p><p>For example, suppose that, while operating a medical device, a user repeatedly changes the way they hold it.</p><p>What can be confirmed through observation is that the user changes their grip during the operation. However, observing that action alone does not explain why the change is necessary.</p><p>The device’s shape or the arrangement of its controls may require the user to change their grip. Alternatively, the change may be needed to alter the direction of operation or the force applied to the device. It is also possible that the operating method reflects the relationship between the device, surrounding equipment, and the working environment.</p><p>Furthermore, changing the grip may be necessary to achieve the intended objective, or it may be done to ensure safety or reliable operation.</p><p>The fact that a user changes their grip therefore does not establish that the action is unnecessary. We need to distinguish between the action confirmed through observation and the reasons why that action is performed.</p><p>On the other hand, if the action is necessary because of the current device’s structure, changing that structure might reduce the need for it or allow the same objective to be achieved through a different method.</p><p>To consider this possibility, it is necessary to understand more than the act of changing one’s grip. What is the user doing before and after the action? What is the purpose of operating the device, and what conditions make that particular action necessary?</p><p>Once these relationships become clearer, it may be possible to consider improvements to operations for which users have never expressed an explicit request.</p><p>However, identifying a possible improvement is not the same as establishing that the action represents a problem that needs to be solved. It is still necessary to determine whether changing the action would allow the underlying objective to be achieved appropriately.</p><p>Observation should also extend beyond the actions of the person directly operating the device.</p><p>Medical devices are used within sequences of clinical procedures involving diagnosis, examination, and treatment. Preparations before use, procedures performed afterward, and interactions with other equipment are therefore important when seeking to understand the conditions in which a device is used.</p><p>For example, another person may be responsible for preparing or assisting with the use of a device. Is that work necessary because of the requirements of the clinical procedure itself? Or is it necessary because of the current device’s structure or method of use?</p><p>If the work is required by the device’s existing structure, modifying that structure may affect not only the person operating the device but also the work performed by others.</p><p>Conversely, a modification intended to simplify one operation might increase the burden associated with another stage, such as preparation or cleanup.</p><p>Observing only the actions of the person directly operating the device may therefore be insufficient to understand what should be improved. Considering the entire clinical procedure and the work performed by everyone involved may reveal other problems or possibilities for improvement.</p><p>The important point is to understand why each action or task is necessary and how it relates to other actions and conditions, rather than treating them as independent pieces of information.</p><p>Even if one task can be eliminated, the overall process has not necessarily improved if the modification creates a need for another task. Conversely, modifying one part of a device may make it possible to improve other activities that did not initially appear to be directly related.</p><p>Considering these relationships draws on the knowledge and experience accumulated in areas such as structure, function, mechanics, materials, and usability.</p><p>For example, if a particular action appears necessary because of the device’s shape or the arrangement of its controls, it becomes possible to consider how the operating method might change if that shape or arrangement were modified.</p><p>Changing how a device is held or the direction in which force is applied may affect its movement and usability. The modification may also influence its relationship with surrounding equipment or other operations.</p><p>Within a multilayered and multidimensional cognitive structure, observing an actual operation also involves perceiving the device’s structure and functions, the reasons why particular actions are necessary, and the possibilities that might arise from modifying the structure as interconnected aspects of the same subject.</p><p>This is different from following a sequence of independent procedures in which observations are first recorded, all information is collected, and only afterward is its meaning analyzed.</p><p>The observed actions and conditions of use are connected to the multilayered and multidimensional cognitive structure that has already been formed. As these relationships reveal possible problems, they also change what needs to be observed next.</p><p>For example, if a particular action appears to be required by the device’s shape, this may reveal a need to determine whether the same action occurs under different operating conditions. If another structure appears capable of changing the operation, it also becomes necessary to consider the conditions under which that alternative structure could function.</p><p>Observation, understanding the problem, considering possible structures, and recognizing what information needs to be confirmed are therefore proceeding simultaneously, influencing one another.</p><p>However, being able to suggest causes or solutions based on an observed phenomenon does not mean that those explanations have been verified. The facts established through observation must be distinguished from hypotheses about their underlying causes.</p><p>Developing a hypothesis may then reveal what additional information needs to be confirmed. That information may, in turn, change our understanding of the causes or solutions previously considered.</p><p>For example, even if an action was initially thought to be necessary because of the device’s shape, observations under different operating conditions may reveal that other factors are involved. Conversely, observing the same action under several conditions may provide clues about what those conditions have in common.</p><p>However, the same action does not necessarily have the same cause in every situation. Nor can a problem observed in one situation automatically be assumed to affect all users.</p><p>The operating methods and problems associated with a medical device may vary depending on the user, clinical procedure, and working environment. It is therefore important to understand the conditions under which a phenomenon was observed and, when necessary, examine the device under different conditions of use.</p><p>By understanding what is common, what differs, and how those differences affect actions and outcomes, it becomes possible to examine the relationships between observed phenomena, device structures, and operating conditions in greater detail.</p><p>In addition to observing actual use, performing similar operations in a simulated environment can also provide useful information about how a device is handled.</p><p>Holding and operating the device directly may reveal aspects of its use that were difficult to understand through observation alone.</p><p>For example, actually operating a device may provide a more concrete understanding of how it can be held comfortably, the direction in which force needs to be applied, and how the device responds when its controls are manipulated.</p><p>Direct operation may also change our understanding of the device’s structure and functions. Understanding the movements and forces required for an operation may reveal other design possibilities.</p><p>However, operating a device in a simulated environment is not equivalent to the experience of healthcare professionals using it in actual clinical practice.</p><p>The necessary actions and the problems encountered may differ depending on the operator’s skills and experience, the clinical environment, and the patient’s condition. The impressions gained from a simulated environment therefore cannot automatically be treated as facts about clinical use.</p><p>Observing actual conditions of use and operating a device in a simulated environment provide different kinds of information. By relating what is learned from both, it becomes possible to develop a more detailed understanding of the device’s structure and operating methods.</p><p>Information obtained through observation and direct operation becomes connected with existing knowledge and experience, updating the multilayered and multidimensional cognitive structure.</p><p>For example, an action initially understood simply as part of the device’s operating method may later appear to be necessary because it compensates for a structural constraint. This may reveal the possibility of reducing that action by changing the structure.</p><p>Conversely, an action initially considered unnecessary may prove to be related to an essential function or to safety. In that case, eliminating the action may no longer appear to be an appropriate improvement.</p><p>In this way, our understanding of observed phenomena and our understanding of a device’s structure and functions change in relation to one another. These changes also affect what we recognize as a problem.</p><p>AI may also contribute to understanding information obtained through observation.</p><p>For example, AI could help organize observation records and compare the similarities and differences among operations and problems encountered under different conditions of use. It could also help organize multiple hypotheses about why a particular action is necessary or examine relationships that had not previously been considered.</p><p>Furthermore, considering observed phenomena in relation to knowledge and technologies used in other fields may reveal alternative explanations or possible solutions.</p><p>Information and hypotheses presented by AI may change how an observed phenomenon is understood. As the possible causes and solutions change, the operating conditions that need further investigation and the information required for analysis may also change.</p><p>However, relationships or hypotheses suggested by AI on the basis of observation records do not necessarily explain what actually occurred. AI may also be unable to make adequate judgments about conditions not included in the records or about the intentions of the people operating the device.</p><p>It is therefore necessary to distinguish between facts established through observation and interpretations or hypotheses generated through AI analysis. Where appropriate, these hypotheses must be examined through additional observations or confirmation with the users involved.</p><p>Even when observation reveals a possible new problem, it is still necessary to consider whether that problem genuinely needs to be solved.</p><p>For example, although it may be possible to reduce the number of actions required for an operation, doing so would not necessarily constitute an appropriate improvement if it compromised an essential function or increased the burden elsewhere.</p><p>Furthermore, even if a designer identifies a possible improvement to an action that users themselves have not regarded as a problem, the actual value of that modification may remain unclear.</p><p>Observation can establish what actions are being performed and the various conditions associated with their use. By connecting this information with existing knowledge and experience, it becomes possible to consider the causes of potential problems and ways they might be improved.</p><p>However, further understanding is needed to determine whether the problem inferred from observation actually exists, what would change if it were solved, and what that change would mean for the user.</p><p>Identifying latent needs involves more than searching for requirements that users have not expressed in words.</p><p>It involves observing actual conditions of use and understanding the purposes and conditions that give rise to the actions and phenomena encountered. By considering these relationships, it becomes possible to identify circumstances that users have not yet recognized as problems, along with possibilities for improvement through methods different from those currently used.</p><p>To do so, it is necessary to distinguish among observed phenomena, interpretations of their causes, and possible solutions while understanding how they relate to one another. Obtaining new information through observation, recognizing possible problems, and considering design possibilities also influence one another within the same multilayered and multidimensional cognitive structure.</p><p>When latent needs and possibilities for improvement become apparent in this way, what should ultimately be achieved? What would constitute the ideal form of the device or procedure?</p><p>Could changing the assumptions underlying existing devices and clinical procedures, rather than simply improving them within their current limitations, reveal value that had not previously been recognized?</p><p>In the next chapter, I will examine what the ideal form should be and the value that has not yet been recognized.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6301386e7d7c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-7-6301386e7d7c">Multilayered and Multidimensional Thinking in Development: Chapter 7</a> was originally published in <a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic">Human–AI Coexistence : Principles for a Symbiotic Future</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multilayered and Multidimensional Thinking in Development: Chapter 6]]></title>
            <link>https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-6-3019cbc3b690?source=rss-b54030f2935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3019cbc3b690</guid>
            <category><![CDATA[medical-devices]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[cognitive-science]]></category>
            <dc:creator><![CDATA[Keita SUZUKI]]></dc:creator>
            <pubDate>Sat, 14 Nov 2026 14:01:02 GMT</pubDate>
            <atom:updated>2026-11-14T14:01:02.139Z</atom:updated>
            <content:encoded><![CDATA[<h4>What Lies Behind Customer Requirements</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*6dZM2VcMUorKlHl-MbiudA@2x.jpeg" /></figure><p>In the previous chapter, I considered how new information can change our understanding of existing relationships and judgments, thereby updating the multilayered and multidimensional cognitive structure itself. This time, I would like to examine how we understand customer requirements, which are an important source of information in product development.</p><p>In product development, customers express a wide variety of requirements. Some concern dissatisfaction with existing products or requests for improvements, while others involve new functions or performance characteristics. Understanding these requirements and incorporating them into appropriate specifications is an important part of development.</p><p>In medical device development, requirements often come from healthcare professionals who use the devices in clinical practice, including physicians, nurses, and clinical laboratory technologists. Through their daily involvement in diagnosis, testing, and treatment, these professionals have direct experience of how devices are used and where difficulties or problems arise.</p><p>Customer requirements therefore provide valuable information for development. However, accurately understanding what has been requested is not necessarily the same as understanding the problem that actually needs to be solved.</p><p>For example, suppose a customer asks for a particular part of an existing device to be modified. If we treat that request directly as a design specification, our consideration focuses on how to modify the specified part. But to determine whether the modification is appropriate for achieving the underlying purpose, we first need to understand why the customer considers it necessary.</p><p>What problem arises when using the current device? What does that problem prevent the customer from achieving? And why does the customer believe that the requested modification is necessary to solve it? Understanding this background may change how we interpret the original requirement.</p><p>Suppose, for example, that a customer asks for a medical device to be made thinner.</p><p>If we consider only those words, reducing the device’s outer diameter becomes the design objective. However, what the customer ultimately wants to achieve may differ depending on why a smaller diameter is needed.</p><p>If the problem is that the current device cannot pass through a narrow space, the objective is to make passage possible. If the customer wants to reduce the burden associated with using the device, we need to understand under what conditions that burden arises. If the problem concerns compatibility with another device, the dimensional and structural requirements necessary for the devices to work together become important.</p><p>All of these situations could lead to the same request to make the device thinner. Yet the problems to be solved and the objectives to be achieved are different.</p><p>And when the objectives differ, the appropriate solutions may differ as well. In some cases, reducing the outer diameter may be necessary. In others, the same objective may be achieved through a different structure or method of use. How the original requirement should be reflected in the design therefore needs to be considered in relation to the underlying problem and purpose.</p><p>This does not mean that the solution proposed by the customer is incorrect. Customers may have a thorough understanding of the operating environment and technical conditions and may request an entirely appropriate modification. In such cases, the requested change may be a necessary condition for achieving the intended purpose.</p><p>There is therefore no reason to assume from the outset that the requested modification is the correct solution, nor to assume that it is an existing premise that should be changed. What matters is understanding why the requirement is necessary and considering its meaning in relation to the underlying objective.</p><p>I would also like to examine the information contained within a customer requirement.</p><p>When customers request a modification, their request may involve phenomena they have experienced, their understanding of the problems associated with those phenomena, and the methods they consider necessary to address them.</p><p>For example, experiencing that operating a device requires considerable force, wanting to reduce that force, and judging that the device’s structure should be modified to achieve this are three different things.</p><p>We can distinguish between what actually occurred and how that occurrence is understood as a problem. Likewise, the objective of solving a problem is not identical to the method selected to achieve it.</p><p>Of course, customers do not necessarily explain these aspects separately. A single requirement may contain their experience, their understanding of the problem, and their judgment about a possible solution. We therefore need to understand whether the customer’s words describe something they experienced, a problem they perceive, or a proposed method for solving that problem.</p><p>It is also necessary to distinguish between a phenomenon the customer reports having experienced and an interpretation of its cause. Even if a particular operation required considerable force, other factors may have contributed to why that force was necessary. Without sufficient information about the cause, we cannot treat the customer’s explanation as an established fact.</p><p>Understanding these distinctions allows us to connect what the customer has said with the phenomena that need to be verified, the problems that need to be solved, and the conditions that need to be considered in the design.</p><p>Furthermore, even the same requirement may have a different meaning depending on the operating environment and intended use.</p><p>Medical devices are used under a variety of conditions, including different clinical procedures, patient conditions, and methods of operation. Something that constitutes a significant problem under one set of conditions may not be a problem under another.</p><p>It is therefore important to understand the circumstances in which a customer requirement arose. What procedure was being performed, and what was the device intended to achieve? Under what conditions did the problem occur, and what did it prevent the user from doing? With this information, we can consider the conditions under which the requested function or performance must be achieved.</p><p>For example, if a customer requests an improvement to a particular operation because a problem occurs only under specific conditions, those conditions need to be understood when considering a solution. On the other hand, if the same problem occurs across a wide range of operating conditions, it may be necessary to examine the device’s fundamental structure or functions.</p><p>However, evidence that a problem occurred under certain conditions does not establish that it is absent under other conditions. We need to distinguish between what has actually been confirmed and what remains unverified when considering the range of conditions to which a requirement applies.</p><p>In medical device development, requirements may also come from people who interact with the same device in different roles.</p><p>For example, the functions emphasized by physicians may not necessarily be the same as the usability or operational requirements emphasized by nurses or clinical laboratory technologists. Their responsibilities and the situations in which they interact with the device differ.</p><p>When different requirements are expressed, this does not necessarily mean that one is incorrect. They may reflect different objectives or operating conditions. Furthermore, satisfying a requirement expressed by one group may affect the work performed by another.</p><p>We therefore need to consider not only each requirement independently but also how the requirements relate to one another within the same device or clinical procedure. What does a modification requested by one person mean for someone in another role? How would that modification affect other conditions involved in using the device? Understanding these relationships allows us to consider what the device as a whole needs to achieve.</p><p>However, this does not mean that all requirements should be combined into a single condition. Different users and objectives may require different conditions. We need to understand why each requirement exists and distinguish between conditions that must be satisfied in common and those that vary according to the circumstances of use.</p><p>Another consideration is that customer requirements are not always communicated directly by the customers themselves.</p><p>In product development, requirements are sometimes conveyed through sales representatives or other intermediaries. In such cases, the information received depends not only on what the customer originally said but also on how the person communicating the requirement understood and organized it.</p><p>For example, details about the operating conditions or the background of a problem may be omitted as the requirement is passed along. Several requests may also be consolidated into a single improvement requirement.</p><p>This kind of organization can help communicate necessary information more clearly. However, the resulting summary may not provide enough information about the objectives or conditions needed to consider the design. In such cases, it becomes necessary to investigate the customer’s original statements or the circumstances in which the device was used.</p><p>Conversely, hearing a requirement directly from the customer does not necessarily mean that we understand its entire background.</p><p>Customers may formulate their requirements on the assumption that the devices and procedures they currently use will remain unchanged. They may also leave certain conditions unexplained simply because those conditions are so familiar from everyday experience that they do not think to mention them.</p><p>We therefore need to understand why a requirement arose, whether it was communicated through a sales representative or heard directly from the customer. Speaking directly with the customer provides an important opportunity to investigate the background, but hearing the requirement firsthand is not the same as fully understanding its meaning.</p><p>The information obtained about customer requirements and their background also becomes connected with the cognitive structure that has already been formed.</p><p>For example, suppose we come to understand the problem underlying a particular customer requirement. By considering how that problem relates to our existing understanding of the device’s structure, functions, and operating conditions, we may begin to interpret the original requirement differently.</p><p>When first hearing the requirement, we might think that the shape of a particular component needs to be changed. However, a deeper understanding of why the problem occurs may reveal a need to consider another part of the structure or the operation of the device as a whole.</p><p>At the same time, considering technical possibilities may reveal ways of solving the problem other than the method requested by the customer. Those possibilities may, in turn, change our understanding of the original requirement and the conditions that ultimately need to be satisfied.</p><p>The important point here is that understanding customer requirements and considering possible solutions are not necessarily independent forms of thought.</p><p>Even while considering the customer’s words and operating conditions, I am drawing on existing knowledge and experience to examine possible causes of the problem and ways it might be solved. And when a possible solution becomes apparent, it may change which operating conditions need to be investigated further or what questions should be asked of the customer.</p><p>Understanding the information and considering the technical possibilities proceed within the same multilayered and multidimensional cognitive structure, influencing one another. My thinking does not follow only a one-way sequence in which I first understand the background of a requirement and then begin considering the design.</p><p>However, recognizing a technically feasible possibility does not necessarily mean that it is an appropriate way to achieve the customer’s objective.</p><p>Even if a new structure can satisfy the requested performance specifications, we still need to determine whether it actually solves the problem under the intended operating conditions. Solving one problem may also introduce another.</p><p>We therefore need to distinguish between understanding the background of a requirement and verifying that a solution developed from that understanding is appropriate. It is important to consider judgments about technical feasibility in relation to our understanding of what the customer is trying to achieve.</p><p>We also need to examine our own interpretations of the problems suggested by the customer’s words.</p><p>If we suspect that a particular problem lies behind a requirement, that interpretation is initially only a hypothesis. Where necessary, we need to confirm whether it is consistent with the actual operating conditions and with what the customer is trying to accomplish.</p><p>Treating the customer’s stated requirement as a fixed design solution can be problematic. But it is equally problematic for a designer to treat an unverified interpretation of the customer’s problem as correct.</p><p>What matters is deepening our understanding of what needs to be achieved by considering the customer’s words, the actual conditions of use, and the relevant technical conditions in relation to one another.</p><p>Nor does understanding the background of a requirement mean that everything the customer has requested can be changed. Some conditions must be satisfied to achieve the intended purpose, while others can be satisfied through different methods of implementation. Understanding this distinction allows us to consider which requirements must be preserved in the design and which objectives can be achieved in other ways.</p><p>I believe that understanding customer requirements involves more than accurately receiving the words in which they are expressed. It also means understanding the circumstances that gave rise to those requirements and what they are intended to achieve.</p><p>To do so, we need to perceive the phenomena experienced by customers, the operating environment, the purpose of the requested modifications, and the technical conditions as interconnected. Understanding these relationships allows us to consider whether directly implementing the original request is appropriate or whether the intended purpose could be achieved through another approach.</p><p>However, even a detailed understanding of the background to customer requirements does not necessarily reveal every problem.</p><p>Customers may not recognize certain circumstances as problems, or they may be unable to express requirements for methods they have never experienced.</p><p>How, then, can we identify problems that customers have not expressed in words or needs they have not yet recognized?</p><p>In the next chapter, I will examine how observing actual conditions of use can help us identify latent needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3019cbc3b690" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-6-3019cbc3b690">Multilayered and Multidimensional Thinking in Development: Chapter 6</a> was originally published in <a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic">Human–AI Coexistence : Principles for a Symbiotic Future</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multilayered and Multidimensional Thinking in Development: Chapter 5]]></title>
            <link>https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-5-120c8d1ae294?source=rss-b54030f2935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/120c8d1ae294</guid>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[medical-devices]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[cognitive-science]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Keita SUZUKI]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 14:01:03 GMT</pubDate>
            <atom:updated>2026-11-13T14:01:03.743Z</atom:updated>
            <content:encoded><![CDATA[<h4>How New Information Updates a Cognitive Structure</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*6dZM2VcMUorKlHl-MbiudA@2x.jpeg" /></figure><p>In the previous chapter, I considered how a multilayered and multidimensional cognitive structure is formed through the interconnections among different kinds of knowledge and experience. This time, I would like to examine what changes, and how, when new information becomes part of an already established cognitive structure.</p><p>Acquiring new knowledge is generally understood as increasing what we know. However, when we perceive the interrelationships among pieces of information, new information can also change the meaning of what we already know and the relationships we previously understood.</p><p>For example, suppose I am considering a structure intended to achieve a particular function. After examining the necessary geometry, materials, and manufacturing methods, I conclude that the structure would be difficult to realize using the processing technologies I currently know. In this situation, the intended function, geometry, material properties, and processing technologies are interconnected within my cognitive structure, and my judgment about the feasibility of the design is based on those relationships.</p><p>Now suppose I learn about a new processing technology. If this technology appears capable of producing a shape that I previously considered difficult to manufacture, what changes within the cognitive structure?</p><p>First, I gain knowledge of the new processing technology. But that is not the only change. A shape that previously seemed difficult to manufacture may now appear feasible. If that shape can be realized, my assessment of the feasibility of the originally intended function and structure also changes.</p><p>Furthermore, if the new technology makes other shapes possible, it may reveal structural possibilities I had not previously considered. I may also become able to consider different methods or more suitable structures for achieving the original function.</p><p>What is happening here is more than the addition of one piece of information about a new processing technology. That information changes previously recognized relationships involving geometry, materials, manufacturing constraints, and the feasibility of achieving particular functions.</p><p>However, the existence of a new processing technology does not necessarily mean that it can be used in an actual design. We still need to determine whether it is compatible with the required materials, whether it can achieve the necessary processing accuracy, and whether other manufacturing conditions can be satisfied.</p><p>Learning about the technology therefore does not establish that the structure is feasible. Rather, it makes it possible to examine a new option for a structure that had previously seemed difficult to realize.</p><p>Nor does learning about a new technology necessarily mean that our previous knowledge was incorrect.</p><p>The judgment that a particular structure would be difficult to realize using conventional processing technologies may still be valid within the conditions and limitations of those technologies. If a new technology offers another possibility, we need to distinguish between the conditions under which the conventional approach remains infeasible and those under which the new approach may be feasible.</p><p>In this way, new information does not necessarily replace our previous understanding. Changes to a cognitive structure may involve clarifying the conditions under which existing knowledge holds, expanding its range of application, or recognizing relationships that were not previously understood.</p><p>These changes may also extend beyond the elements directly associated with the new information.</p><p>For example, if a processing technology increases the range of shapes that can be produced, it may also change the available material options. Greater freedom in geometry may reveal the possibility of achieving a function through a different structure, rather than through the combination of multiple components previously required.</p><p>As a result, the range of possibilities we can consider may change with respect to the relationships among components, manufacturing methods, and usability. We may even need to reconsider requirements that were originally defined on the assumption that the conventional structure would be used.</p><p>A single piece of new information can therefore affect more than the element to which it directly relates. Its effects may extend to other connected elements and relationships, changing the possibilities that can be considered within the overall cognitive structure.</p><p>There is another aspect I would like to examine here: the meaning of new information also depends on the cognitive structure that has already been formed.</p><p>For example, I may have known about a particular technology for some time. However, if I do not sufficiently understand where it can be applied or how it relates to other technologies, I may not recognize its relevance to the design I am currently considering.</p><p>Later, knowledge from another field or a new understanding of a design may reveal a relationship between that familiar technology and the structure under consideration. In this case, the technology itself has not changed. What has changed is my understanding of how it relates to other knowledge.</p><p>Information that changes a cognitive structure is therefore not necessarily limited to newly developed technologies or facts encountered for the first time. Even familiar information can acquire a different meaning when relationships that were previously unrecognized become apparent.</p><p>The same information may also lead to different considerations depending on what knowledge and experience a person already has and how that knowledge is interconnected.</p><p>If the knowledge needed to understand certain information is missing, it may be difficult to appreciate its significance. On the other hand, when related knowledge and experience are already available, the information can be considered in connection with existing understanding, potentially revealing new possibilities or differences from previous assumptions.</p><p>The important distinction here is between receiving new information and understanding what that information means within a cognitive structure.</p><p>Even after obtaining information, we may not be able to use it in a new design if we do not understand how it relates to existing knowledge and experience. Conversely, information that has long been available may reveal previously unconsidered design possibilities once its relationships with existing knowledge become understood.</p><p>As the cognitive structure changes, the information we need also changes.</p><p>Consider the earlier example of the processing technology. Suppose a structure previously judged difficult to realize using conventional methods now appears potentially feasible because of a new processing technology.</p><p>Until then, the structure may not have been examined in detail because it was considered impractical to realize. Once its feasibility becomes a possibility, however, there is a reason to investigate it more closely.</p><p>For example, additional information may be needed about the accuracy of the new processing technology, the materials to which it can be applied, and its manufacturing constraints. If the structure can be realized, we also need to reconsider what functions and performance it might actually provide.</p><p>If this additional information reveals new constraints or possibilities, the cognitive structure changes further. In some cases, it may become necessary to examine a different condition more closely than one previously considered important.</p><p>Information gathering and the updating of a cognitive structure therefore do not operate in only one direction.</p><p>Our existing cognitive structure influences what information we recognize as necessary. The information we obtain can then change that structure, which may reveal the need for additional information or change the significance of information we already possess.</p><p>However, this does not mean that we repeatedly perform separate procedures in which we finish gathering information, update the cognitive structure, and then begin searching for the next piece of information. Even while investigating new information, I am considering how it relates to existing knowledge. And while considering those relationships, I may recognize further questions that need to be investigated or new possibilities worth exploring.</p><p>Information exploration, analysis, understanding relationships with existing knowledge, and considering new possibilities proceed simultaneously within the same cognitive structure, continually influencing one another.</p><p>When we consider how this cognitive structure operates, collaboration with AI also becomes significant.</p><p>AI can be used to explore information across a wide range of specialized fields and analyze the characteristics of different technologies and the relationships among them. It can also help investigate fields in which my knowledge is limited or organize information from perspectives different from those reflected in my existing understanding.</p><p>AI can therefore serve as a means of obtaining new information while also helping reveal relationships that I had not previously recognized.</p><p>For example, suppose I am examining a particular structure and AI introduces a technology used in another field. If that technology might be applicable to the structure under consideration, I can reconsider the existing constraints and possible methods of implementation.</p><p>As I examine that possibility, the information and analysis I need from AI may also change. I might need a more detailed understanding of the principles underlying the suggested technology, or further analysis of its similarities to and differences from the current structure.</p><p>In this way, information and analysis obtained from AI can change my cognitive structure, while changes in that structure also alter what I ask AI to investigate. Collaboration with AI is not simply a one-way process of receiving information. Exploring information, considering its relationships with existing knowledge, and examining new design possibilities influence one another throughout the process.</p><p>However, even if information or analysis presented by AI reveals a new possibility, that does not necessarily mean the information is correct. Nor does an accurate explanation of a technology establish that the technology can be applied to the design under consideration.</p><p>It is therefore necessary to examine the evidence and conditions of applicability associated with information provided by AI. When appropriate, I need to consult the original technical documentation or research findings and distinguish between what has been verified and what remains an inference or hypothesis.</p><p>This consideration is not limited to information obtained from AI.</p><p>New information may include well-established facts, results that hold only under particular conditions, or hypotheses that have not yet been verified. Different sources may also present information that appears contradictory.</p><p>In such cases, it is necessary to examine the conditions and evidence underlying each claim rather than accepting one without further consideration. If the apparent contradiction arises from differences in the conditions under which the results were obtained, understanding those differences may allow both pieces of information to be interpreted appropriately.</p><p>On the other hand, if the evidence and conditions do not allow us to determine which claim is correct, we need to preserve that uncertainty in our understanding. Obtaining information does not necessarily resolve every question.</p><p>Updating a cognitive structure also does not mean that every new piece of information must change our previous understanding. New information may support what we already understood or allow us to explain an existing relationship in greater detail.</p><p>What matters is understanding how new information relates to the knowledge and experience we already have. As a result, our understanding of existing relationships may deepen, or the conditions under which they hold and their range of applicability may change, revealing new possibilities.</p><p>I believe that our understanding of things continually changes through this interaction between information and cognitive structures.</p><p>New information may reveal relationships that we had not previously recognized. Recognizing those relationships may then change the meaning of familiar information and what additional information we need. These changes may also reveal problems or possible solutions that were not considered at the outset.</p><p>This is not a process limited to designing something new. When we try to understand or think about anything, new information can change our previous perceptions and judgments. Within a multilayered and multidimensional cognitive structure, these changes extend beyond individual pieces of information to the relationships among them.</p><p>As new information becomes available, it may change the meaning or conditions of relationships we previously understood, altering the possibilities we can consider. The resulting changes to the cognitive structure may also change our understanding of what else we need to know.</p><p>How, then, are customer requirements understood within such a cognitive structure? What is the difference between knowing what a customer has requested and understanding the circumstances behind that request and the purpose that should ultimately be achieved?</p><p>In the next chapter, I will examine what lies behind customer requirements.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=120c8d1ae294" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-5-120c8d1ae294">Multilayered and Multidimensional Thinking in Development: Chapter 5</a> was originally published in <a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic">Human–AI Coexistence : Principles for a Symbiotic Future</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multilayered and Multidimensional Thinking in Development: Chapter 4]]></title>
            <link>https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-4-d3f2aff3f098?source=rss-b54030f2935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3f2aff3f098</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[cognitive-science]]></category>
            <category><![CDATA[medical-devices]]></category>
            <dc:creator><![CDATA[Keita SUZUKI]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 14:01:02 GMT</pubDate>
            <atom:updated>2026-11-12T14:01:02.863Z</atom:updated>
            <content:encoded><![CDATA[<h4>How Knowledge and Experience Form a Cognitive Structure</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*6dZM2VcMUorKlHl-MbiudA@2x.jpeg" /></figure><p>In the previous chapter, I examined a multilayered and multidimensional cognitive structure in which numerous kinds of information and conditions are interconnected and change simultaneously and dynamically. This time, I would like to consider how such a cognitive structure is formed through knowledge and experience.</p><p>When designing something new, we draw on various kinds of knowledge and experience accumulated over time. These include specialized knowledge of material properties, physical laws, mechanical structures, processing methods, and manufacturing technologies. Designs considered in the past, together with the results obtained from them, also provide a basis for our judgments.</p><p>However, accumulating a large amount of knowledge and experience is not necessarily the same as being able to use them to develop new structures.</p><p>As I have discussed in the preceding chapters, design requires an understanding of how individual pieces of information relate to one another, as well as an understanding of the information itself. Our understanding of these interrelationships is also formed through the knowledge and experience we have acquired.</p><p>For example, suppose we learn about the strength, elastic properties, and processability of a particular material. Knowing these characteristics is important, but actual design also requires us to consider what shape the material should take and under what conditions it should be used to achieve the required functions.</p><p>Some of this understanding comes from specialized knowledge of physical laws and material properties. Other aspects come from actual design and evaluation experience. We can also learn from structures developed by others and the circumstances in which those structures are used.</p><p>What matters here is that knowledge and experience do not simply accumulate as independent pieces of information. Through their interconnections, they form the cognitive structure that allows us to understand what we are designing.</p><p>I would first like to consider the role of my own design experience.</p><p>When designing a new structure, I draw on existing knowledge and experience to consider what combinations of shapes, materials, and structures might achieve the required functions. Prototyping and evaluation then allow me to examine whether the predicted results can actually be obtained.</p><p>When the expected results are obtained, they provide confirmation, within a certain range, that the proposed structure works under the conditions considered. However, a structure that works under one set of conditions will not necessarily work under another. It is therefore important to understand the materials, geometry, and operating conditions under which those results were obtained.</p><p>When the results differ from the predictions, I need to consider the possible causes. Was my understanding of the material properties insufficient? Had I misunderstood the forces acting on the structure? Or were other factors, such as manufacturing methods or operating conditions, involved?</p><p>Of course, an unexpected result does not automatically reveal its cause. Several factors may be involved, and identifying the cause may require gathering additional information or conducting further evaluations under different conditions.</p><p>The results obtained in this way, together with an understanding of their causes, can be used when considering other designs. Even the experience of finding that a structure works under certain conditions but not under others becomes useful knowledge when we understand what those conditions have in common and how they differ.</p><p>What we gain from design and evaluation experience therefore includes more than completed structures and measurement results. It also includes an understanding of the conditions and interrelationships that produced those results.</p><p>Design experience also deepens our understanding of more than technical relationships involving materials and structures. It is connected to how we understand the problem itself, including what we intended to achieve through a particular design.</p><p>For example, even if a structure that achieves the requested function is technically feasible, we may need to reconsider the original requirements or our understanding of the problem if the structure does not accomplish the underlying purpose. Conversely, discovering that a new structure can achieve a different function may reveal possibilities that were not considered when the original objective was defined.</p><p>In this way, the knowledge gained from design experience includes both an understanding of structural feasibility and an understanding of what should be achieved. These are also interconnected. Through design and evaluation experience, we can deepen our understanding of what is technically possible while also reconsidering the functions and value we seek to realize.</p><p>Our cognitive structures, however, are not formed solely through direct personal experience.</p><p>We can also learn a great deal from products and structures designed by others. Particularly effective designs often contain solutions developed to achieve required functions under a variety of constraints.</p><p>For example, examining a product may allow us to understand the materials used, the shapes of its components, and how those components are assembled. This alone provides useful design knowledge, but what I am particularly interested in understanding is why that structure was adopted.</p><p>What was the product designed to achieve? What conditions needed to be satisfied, and what constraints existed? Why were those particular materials, shapes, and structures selected under those conditions?</p><p>Considering these questions allows us to examine not only the characteristics of the finished structure but also the conditions that make it feasible and the technical relationships used to address the underlying problem.</p><p>However, examining a finished product does not necessarily reveal everything its designer thought or the judgments made during development. If records of the development process or technical documentation are available, they can provide valuable information. Without sufficient evidence, some explanations for why a particular structure was adopted remain speculative.</p><p>We therefore need to distinguish between the structures, functions, and conditions of feasibility that can be verified and our interpretations of the designer’s intentions. With that distinction in mind, examining the physical phenomena and manufacturing conditions associated with a structure can provide considerable knowledge from the work of other designers.</p><p>Knowledge gained from other designs is also useful for purposes beyond reproducing the same structures.</p><p>For example, if we attempt to use the shape of an existing product without changing it, its applicability is limited by the conditions under which that shape can function. However, if we understand the physical phenomena involved and the conditions under which the structure achieves its intended function, we may be able to use that knowledge when considering a different structure.</p><p>If we determine that a mechanical relationship used to achieve a particular function can also apply to another structure, it may be possible to achieve a similar function using different shapes or materials. However, recognizing a common relationship does not mean that the technology can be transferred without modification. Differences in materials, dimensions, operating environments, or performance requirements mean that feasibility must be reconsidered under the new conditions.</p><p>The same approach applies when learning from technologies developed in other fields.</p><p>Products may differ greatly in purpose and appearance while relying on common physical phenomena. Materials or processing technologies widely used in one field may also be relatively unfamiliar in another.</p><p>For this reason, I find it valuable to learn about technologies and designs outside the field directly related to the product I am developing. However, simply learning that a technology exists in another field does not necessarily lead to a new design. By understanding what that technology achieves and the principles and conditions that make it work, we can consider what it has in common with the current design, how it differs, and which conditions would need to change for it to be applied.</p><p>What becomes part of the cognitive structure is therefore more than knowledge of a technology from another field. It also includes new relationships between that technology and the physical phenomena, structures, and functions we already understand.</p><p>I also consider an understanding of technological history important in the formation of cognitive structures.</p><p>The products and technologies we use today did not exist in their present forms from the beginning. Different materials, structures, and manufacturing methods were used in the past, and technologies developed as various technical problems were addressed.</p><p>Learning what older products looked like and what technologies they used certainly adds to our technical knowledge. However, what I consider particularly important is understanding what problems existed under the technological conditions of the time and how people attempted to solve them.</p><p>For example, suppose that, during a particular period, limitations in material properties or manufacturing technologies made a certain structure difficult to realize. If new materials or processing methods subsequently overcame those limitations and made the structure feasible, we can examine what changed to make that new possibility available.</p><p>Understanding technological developments in this way allows us to learn what constituted a constraint in the past, how particular technologies changed those constraints, and what became possible as a result.</p><p>The problems themselves may also change as technology develops. Overcoming an existing constraint may make different functions or applications conceivable, while also introducing new technical challenges.</p><p>However, we cannot assume that technological development was inevitably moving toward its present outcome simply because a particular technology exists today. The problems recognized by designers at the time, and the options available to them, depended on the technological and social conditions in which they worked.</p><p>When learning from technological history, it is therefore important to distinguish between developments that can be verified and interpretations of the problems and judgments behind them. By considering the relevant circumstances, we can deepen our understanding of how both technological constraints and the ways problems were understood changed over time.</p><p>The knowledge and experience gained in these different ways are not held independently according to where they came from.</p><p>Knowledge acquired through my own design experience may help me understand a structure developed by someone else. Learning about a technology from another field may allow me to understand a phenomenon I previously encountered in a different way. Understanding how technological constraints changed in the past may also influence which conditions I consider changeable in a current design.</p><p>For example, when we recognize that different products use the same physical phenomenon, our knowledge of those products becomes connected through that common physical relationship. Conversely, learning that the same technology produces different results under different operating conditions adds those differences to our cognitive structure as well.</p><p>The important distinction here is between identifying common features and treating different examples as though they were identical. Understanding what is shared, what differs, and how those differences affect the results allows knowledge gained from one example to be considered for use in another design.</p><p>Some knowledge and experience may also involve relationships whose causes or conditions are not yet fully understood. Even when we know that a particular result was obtained, we cannot treat our explanation of that result as established if its cause remains unclear. Distinguishing what has been confirmed from what remains uncertain is also important when considering a design.</p><p>From this perspective, forming a multilayered and multidimensional cognitive structure is different from simply accumulating knowledge and experience.</p><p>My own design experience, the designs of others, technologies from different fields, and historical technological developments all provide information from different sources. However, the knowledge gained from these sources becomes interconnected within the same cognitive structure through similarities and differences, causal relationships, conditions of feasibility, and connections with existing knowledge and experience.</p><p>These relationships are not fixed by the order in which knowledge was acquired or the field from which it came. When considering a particular technology, my own experience, designs developed by others, and knowledge from different fields may all be perceived as information relevant to the same problem. The ways in which these different kinds of knowledge are interconnected allow me to consider various possibilities for structures that do not yet exist.</p><p>This does not mean that acquiring new knowledge and connecting it to existing knowledge are separate procedures performed one after another. Even while understanding something new, I am considering how it relates to the knowledge and experience I already have. Considering those relationships may also change both the meaning of the new information and my previous understanding.</p><p>I believe that these interconnections among knowledge and experience, and the many relationships they form, provide an important foundation for the multilayered and multidimensional cognitive structure.</p><p>What, then, changes when new information becomes available within an already established cognitive structure? How does acquiring new knowledge differ from simply adding another piece of information to that structure?</p><p>In the next chapter, I will examine more closely what it means for new information to update a multilayered and multidimensional cognitive structure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3f2aff3f098" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-4-d3f2aff3f098">Multilayered and Multidimensional Thinking in Development: Chapter 4</a> was originally published in <a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic">Human–AI Coexistence : Principles for a Symbiotic Future</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multilayered and Multidimensional Thinking in Development: Chapter 3]]></title>
            <link>https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-3-0e5ef150f46d?source=rss-b54030f2935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e5ef150f46d</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[medical-devices]]></category>
            <category><![CDATA[cognitive-science]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[philosophy]]></category>
            <dc:creator><![CDATA[Keita SUZUKI]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 14:01:03 GMT</pubDate>
            <atom:updated>2026-11-11T14:01:03.245Z</atom:updated>
            <content:encoded><![CDATA[<h4>Simultaneous Changes Within a Multilayered and Multidimensional Cognitive Structure</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*6dZM2VcMUorKlHl-MbiudA@2x.jpeg" /></figure><p>In the previous chapter, I examined the difference between understanding individual pieces of information and perceiving the relationships among them. This time, I would like to consider how numerous relationships of different kinds are perceived within thought itself.</p><p>I have been using the term “multilayered and multidimensional cognitive structure” to explain how I perceive things and think about them. By this, I mean that various kinds of knowledge and information, together with their interrelationships, are perceived as an integrated whole that changes dynamically.</p><p>For example, when designing a new medical device, its three-dimensional shape and movements appear in my mind almost as visual images. I can picture the shapes of its components, how they fit together, and which parts move in which directions. Even when the device does not yet exist, I can consider its structure and movement in three dimensions.</p><p>However, what I perceive is not limited to images of shapes and movements. I also recognize the forces acting on the structure, the properties of the materials, whether the required functions can be achieved, and how the components could be processed and manufactured. The device’s usability and its relationship to the conditions in which it will be used are also part of my understanding of the same design.</p><p>An important point here is that not everything I perceive necessarily takes the form of words or images. While shapes and movements appear as three-dimensional images, I can understand mechanical relationships, material properties, and manufacturing constraints without necessarily converting them into images or expressing them in words. These aspects do not exist separately in my mind. They are interconnected as parts of the same design.</p><p>For example, when considering the shape of a component, I also recognize the forces that would act on it, where deformation might occur, and how it relates to other components. When I change its shape, I perceive the resulting changes in how forces are transmitted, how the components move, and how they interact with one another as part of the same whole.</p><p>This feels different from imagining a modified shape first and then reconsidering mechanics, materials, and manufacturing conditions one by one. Changing the shape and recognizing how that change affects related elements occur simultaneously.</p><p>Of course, this does not mean that I can accurately determine every outcome through cognition alone. Calculations, analyses, or tests may be necessary to confirm dimensions, strength, and other characteristics with sufficient accuracy. What I want to explain is that, while considering a design, I perceive its geometry, physical behavior, functions, and technical conditions as interconnected aspects of the same structure.</p><p>Why, then, do I describe this kind of cognition as “multilayered and multidimensional”?</p><p>First, by “multilayered,” I mean that different kinds of information about the same object are perceived as overlapping aspects of a single whole.</p><p>In medical device design, for example, we can consider a device in terms of its geometry, functions, mechanics, material properties, manufacturability, or usability. Each of these aspects also involves conditions that must be satisfied for the product to be feasible, as well as relationships with other aspects.</p><p>Consider a particular shape. It is a physical structure intended to perform a required function, but it also has mechanical properties and is subject to constraints imposed by materials and manufacturing methods. Even when focusing on its geometry, the other aspects connected to that geometry are not excluded from consideration.</p><p>The layers I refer to, therefore, are not independent collections of information that are accessed one at a time as needed. Rather, they are a way of distinguishing different kinds of information perceived about the same object while recognizing that those kinds of information remain interconnected.</p><p>By “multidimensional,” I mean that a design cannot be understood through a single condition or measure. It involves numerous different conditions and variables that must be considered together.</p><p>Even when considering geometry alone, there are many variables, such as length, thickness, angle, and curvature. A device may also need to perform several functions or meet multiple performance requirements. Furthermore, the behavior of the same structure may change depending on the forces acting on it or the environment in which it is used.</p><p>These conditions and variables are not necessarily independent. Changing one dimension may affect other dimensions, mechanical properties, or manufacturing conditions. The conditions required to achieve one function may also be related to those required for another.</p><p>In this sense, “multilayered” refers to the different kinds of aspects through which an object can be understood, while “multidimensional” refers to the many conditions and variables associated with those aspects. However, the two are not independent. A condition associated with one aspect may be related to a condition associated with another, and these interrelationships form a single cognitive structure.</p><p>Nor am I suggesting that cognition literally consists of clearly separated layers or a countable number of dimensions. The term “multilayered and multidimensional” is intended to describe how I perceive many different kinds of information, conditions, and relationships as an integrated whole.</p><p>What, then, happens when one element changes within this cognitive structure?</p><p>Suppose I change the shape of a component to achieve a particular function. This change affects the relative positions and movements of the components. It may also alter mechanical conditions and manufacturing constraints. These changes, in turn, can affect whether the originally intended function remains achievable.</p><p>The modified structure may also reveal the possibility of achieving a different function. Conversely, it may introduce a new constraint in an area that previously appeared to present no problem.</p><p>What matters here is that changing one element can affect not only the elements directly connected to it, but also relationships further beyond them. A change in one component’s shape may alter the conditions affecting another component, which may then change the feasibility of an entirely different function or structure.</p><p>These relationships do not necessarily operate in only one direction. Considering a structure may change my understanding of the functions it could achieve, while considering a function may change which structures appear possible. Changing one condition may affect another, and that change may lead me to reconsider the original condition.</p><p>Consequently, when designing something, I am not simply checking whether individual conditions are satisfied within a structure decided upon in advance. Considering one structure can also reveal possibilities for different structures. Nor do these possibilities necessarily exist as completely separate design proposals. Within the same cognitive structure, I perceive them as different structures that could become feasible depending on which conditions are changed.</p><p>This is an important point to preserve when explaining the thinking involved in design.</p><p>For example, it is relatively easy to describe a development process as a sequence: consider the required functions, determine the shapes needed to achieve them, examine materials and mechanical conditions, and then assess whether the design can be manufactured.</p><p>However, my actual thinking does not proceed by completing consideration of the functions before turning to geometry, and then moving on to materials and mechanics. Even while considering functions and shapes, I remain aware of their relationships with materials and manufacturing methods. A change in one condition may also change how I understand the functions or shapes themselves.</p><p>The same applies to gathering information. My thinking does not follow only a sequence in which I collect all the necessary information before designing and then evaluate the result at the end. Considering a design may reveal additional information that needs to be obtained. New information may also change previously recognized relationships, making different structures seem possible.</p><p>Information gathering, problem understanding, structural exploration, and feasibility assessment can be described as different activities. In my actual cognition, however, they are connected within the same multilayered and multidimensional cognitive structure. They influence one another and proceed simultaneously.</p><p>This does not mean that I consciously consider every piece of information and every condition in equal detail at all times. When working on a design, I may examine a particular shape or function closely, or direct my attention toward a specific technical problem.</p><p>Even then, the aspect receiving my attention is not isolated from the other elements. Related conditions and relationships remain part of the cognitive structure while I consider that aspect. When necessary, I can examine those relationships in greater detail.</p><p>Nor is every piece of information or every relationship within the cognitive structure necessarily accurate. If my understanding of a particular relationship is incomplete or necessary information is missing, uncertainty remains in the judgments involving that relationship. This uncertainty may also make it difficult to determine whether other connected elements are feasible.</p><p>For this reason, I need to distinguish between considering a structure feasible in my mind and having confirmed that it is feasible in reality. Judgments made during design are based on accumulated knowledge and experience, and their accuracy must be verified through analysis or experimentation when necessary.</p><p>This cognitive structure also does not remain fixed once it has formed.</p><p>Suppose I learn about a property or method of implementation associated with a technology that I had not previously known. This information may do more than add another piece of knowledge. It may also change how I understand the structures, functions, and constraints related to that technology. A structure previously considered infeasible may become a possibility worth exploring.</p><p>In such a case, the change is not limited to the part of the cognitive structure where the new information was introduced. The meaning of other connected elements and the relationships among them may also change. These changes can reveal further possibilities or new questions that need to be investigated.</p><p>I therefore regard a multilayered and multidimensional cognitive structure as something that continually changes through new information and thought, rather than as a fixed collection of previously established knowledge and relationships.</p><p>The cognitive structure I have described here is a concept I use to explain my own experience of thinking. My account of perceiving shapes, functions, and various technical conditions as an integrated whole, with their relationships changing simultaneously, describes how I experience these processes. It does not establish how information is actually processed within the brain.</p><p>Although I have used medical device design as an example, this cognitive structure is not a particular reasoning procedure that I apply specifically to design. For me, it is the basic way in which I perceive, understand, and think about things. Medical device design provides a relatively clear way to explain it because these cognitive processes are connected to tangible shapes, functions, and questions of technical feasibility.</p><p>What I describe as a multilayered and multidimensional cognitive structure is thus a single, integrated form of cognition in which numerous kinds of information and conditions are interconnected, and their relationships change simultaneously and dynamically. Understanding information, considering problems, and recognizing possibilities for new structures are different aspects of this same cognitive structure.</p><p>But what forms the basis of such a cognitive structure? How do the knowledge and experiences accumulated over time become interconnected to form a structure through which new possibilities can be considered?</p><p>In the next chapter, I will examine how knowledge and experience contribute to the formation of a multilayered and multidimensional cognitive structure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e5ef150f46d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-3-0e5ef150f46d">Multilayered and Multidimensional Thinking in Development: Chapter 3</a> was originally published in <a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic">Human–AI Coexistence : Principles for a Symbiotic Future</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multilayered and Multidimensional Thinking in Development: Chapter 2]]></title>
            <link>https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-2-ae89bc19fa5f?source=rss-b54030f2935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae89bc19fa5f</guid>
            <category><![CDATA[medical-devices]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[cognitive-science]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Keita SUZUKI]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 14:01:03 GMT</pubDate>
            <atom:updated>2026-11-10T14:01:03.422Z</atom:updated>
            <content:encoded><![CDATA[<h4>Perceiving Relationships</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*6dZM2VcMUorKlHl-MbiudA@2x.jpeg" /></figure><p>In the previous chapter, I considered why developing something new requires an understanding of the relationships among different areas of knowledge, as well as knowledge of the individual fields themselves. This time, I would like to examine the difference between possessing information or knowledge and perceiving the relationships among them.</p><p>Designing a new product requires knowledge across a wide range of fields, including material properties, physical laws, mechanical structures, processing methods, and manufacturing technologies. We also need to understand the product’s intended purpose, the environment in which it will be used, and the functions it must perform.</p><p>Having sufficient knowledge in these areas is certainly important. However, knowing a great deal about individual subjects is not necessarily the same as being able to combine that knowledge to create a new structure.</p><p>Suppose we have a thorough understanding of a particular material. Knowing its strength, elastic properties, and processability provides a foundation for considering designs that use it. In actual design, however, the behavior of a component is not determined by the material’s properties alone. It also depends on the shape given to the material, how it is combined with other components, and the conditions under which it is used.</p><p>Even if two components are made from the same material and have identical dimensions, they may deform or move differently depending on how they are supported, the direction of the forces acting on them, and how they are connected to other components. The effect of that deformation on the overall function of a device also depends on the surrounding structure and operating conditions.</p><p>Knowing the material properties and dimensions, therefore, is not enough to understand how the entire product will behave. We also need to understand how each element interacts with the others under particular conditions.</p><p>This reveals an important distinction between understanding pieces of information individually and understanding how they relate to one another.</p><p>For example, suppose we know that a particular material has a high elastic modulus and that a component has relatively small dimensions. These two pieces of information alone do not tell us whether a component made from that material, with those dimensions, will perform the required function.</p><p>If we understand how material properties relate to shape and dimensions, how applied forces relate to deformation, and how that deformation affects function, we can begin to determine the conditions under which the intended purpose can be achieved.</p><p>Understanding one relationship, however, is not always sufficient. We might determine that a particular combination of material and dimensions provides the necessary stiffness under certain conditions, only to find that the dimensions make manufacturing difficult or prevent the component from being assembled with other parts.</p><p>In this case, our understanding of the relationship between the material and its dimensions is not necessarily incorrect. Rather, that relationship alone does not provide enough information to determine whether the product as a whole is feasible. Design requires us to understand not only the relationships between individual elements but also how those relationships connect with one another.</p><p>These relationships can take different forms.</p><p>For example, changing a component’s dimensions may alter its stiffness. This is a physical causal relationship. In other cases, the dimensions of one component may be constrained by those of another component with which it must fit. There are also functional relationships in which several components perform different roles and, through their combination, achieve a particular function.</p><p>Furthermore, even if a structure is technically feasible, it may fail to perform its intended function adequately because of the way people operate it or the environment in which it is used.</p><p>These relationships are not all of the same kind. Some are causal relationships in which a change in one element affects another. Others involve constraints that must be satisfied for a structure to be feasible, or functional relationships in which multiple elements work together to achieve a particular result. What matters is understanding the nature of each relationship and how the different relationships are interconnected.</p><p>Knowing that two elements are related is also not enough if we do not understand the conditions under which that relationship holds. Without that understanding, we may not be able to apply the relationship appropriately in design.</p><p>Suppose that increasing a component’s dimensions allows a particular structure to achieve the required strength. The same approach will not necessarily work in a different structure. Changes in the material, loading conditions, or the way the component is supported can alter the effects of changing its dimensions.</p><p>When applying knowledge gained from a previous design to a new one, we therefore need to understand which conditions are shared and which are different. Understanding the relationships involved allows us to judge whether a relationship established in an earlier design can be applied directly or whether it needs to be reconsidered under the new conditions.</p><p>By perceiving relationships, I mean more than simply knowing that two pieces of information are connected. It means understanding the conditions under which a relationship holds and how a change in one element affects another.</p><p>To do this, we also need to understand what the individual pieces of information actually mean.</p><p>For example, consider a numerical value representing the strength of a material. If we do not understand the test conditions under which that value was obtained, it may be difficult to determine whether it can be applied to an actual design. The value itself may be correct, but different conditions of use may produce different results from those expected.</p><p>In this sense, correctly understanding information and understanding the relationships within which that information can be used are closely connected.</p><p>So far, I have distinguished between information and relationships for the purpose of explanation. In practice, however, knowledge itself often already includes relationships. Understanding a material’s properties, for example, also involves understanding how that material responds under different conditions.</p><p>I am therefore not suggesting that information or knowledge and their interrelationships should be treated as entirely separate categories. The question I want to explore is how extensively our understanding of individual subjects is connected to other aspects of the overall design.</p><p>Suppose we can explain the materials, manufacturing methods, and functions of the individual components in a particular structure. This is important knowledge for understanding that structure. However, determining how a change to one part would affect the others requires an additional understanding of the relationships among those elements.</p><p>If we can also consider how such a change might introduce new constraints or make different functions possible, we can begin to explore new structures rather than simply understand an existing one.</p><p>Of course, understanding relationships does not mean that we can accurately predict every possible change. If necessary information is missing or a relevant phenomenon is not yet fully understood, our predictions will retain some uncertainty. In such cases, we need to distinguish between what is already known and what still needs to be investigated.</p><p>Design also requires us to consider the purpose we are trying to achieve. Even when using the same materials or structures, different intended functions may change which properties matter most and what ranges of conditions are acceptable. A characteristic that presents a problem for one purpose may be entirely acceptable for another.</p><p>Information and relationships in design are therefore also connected to the intended purpose and the conditions of use. What are we trying to achieve, and what conditions must be satisfied to achieve it? The answers determine how the same knowledge or technology can be applied to a particular design.</p><p>From this perspective, designing a new structure requires more than knowing individual pieces of information. We need to understand how they are connected. This involves recognizing what materials, shapes, functions, physical phenomena, manufacturing methods, and operating conditions mean, as well as how they affect one another.</p><p>With an understanding of these relationships, we can also consider what might happen when a particular condition changes, even in a structure that does not yet exist. By drawing on accumulated knowledge, we can anticipate potentially feasible structures and problems that may arise.</p><p>I believe this ability to perceive interrelationships is an important foundation of the thinking involved in developing something new.</p><p>But how are these numerous relationships, each with different characteristics, actually perceived in thought? What is the difference between understanding individual relationships separately and perceiving them together as a multilayered and multidimensional cognitive structure?</p><p>In the next chapter, I will examine the multilayered and multidimensional cognitive structure itself in greater detail.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae89bc19fa5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-2-ae89bc19fa5f">Multilayered and Multidimensional Thinking in Development: Chapter 2</a> was originally published in <a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic">Human–AI Coexistence : Principles for a Symbiotic Future</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multilayered and Multidimensional Thinking in Development: Chapter 1]]></title>
            <link>https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-1-eee4aae19f55?source=rss-b54030f2935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/eee4aae19f55</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[cognitive-science]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[medical-devices]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Keita SUZUKI]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 14:01:02 GMT</pubDate>
            <atom:updated>2026-11-09T14:01:02.620Z</atom:updated>
            <content:encoded><![CDATA[<h4>What Does It Mean to Develop Something New?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*6dZM2VcMUorKlHl-MbiudA@2x.jpeg" /></figure><p>What does it mean to develop something new?</p><p>Product development is generally described as a series of activities: identifying customer requirements, defining specifications, designing, prototyping, evaluating, and ultimately completing a product. In the case of medical devices, additional activities are required, including verifying safety and effectiveness, meeting regulatory requirements, and establishing a system for mass production. Carrying out these activities properly is essential to bringing a product into practical use.</p><p>However, understanding the development process is not necessarily the same as understanding the thinking required to create a new product. A development process describes the activities needed to complete a product. Creating something new also requires us to determine what should be developed in the first place and how it can be achieved.</p><p>Suppose a customer requests an improvement to a particular part of an existing product. Analyzing that request, defining the necessary performance, and modifying the design to meet those requirements are all important aspects of development. However, making the requested improvement does not necessarily resolve the underlying problem.</p><p>Customer requests are often based on assumptions about the products currently in use and how those products are used. When a problem arises with an existing method, customers may request improvements within the framework of that method. Such requests reflect how customers understand the problem, but they do not necessarily capture its underlying nature.</p><p>For this reason, when receiving a customer request, it is important to understand not only what has been requested but also the circumstances that led to it. What is the customer trying to achieve? What problem has arisen, and why does the customer believe that a particular improvement is necessary to resolve it? Examining this background may reveal that the problem requiring attention lies somewhere other than where the original request suggests.</p><p>There may also be problems that customers themselves have not recognized. When people become accustomed to a particular device or procedure, they may accept inconvenience or unnecessary effort as an unavoidable part of using it. In medical device development, observing clinical practice, including how healthcare professionals operate devices and carry out procedures, can reveal problems that have not been expressed in words and needs that have not yet been recognized.</p><p>Understanding such problems also requires considering what the device or procedure should ideally be like. If we think only about improving an existing method, we may remain constrained by the limitations of that method itself. By reconsidering the original purpose of the device or procedure, we may discover that a different approach could achieve a more desirable outcome.</p><p>At the same time, exploring possible solutions may reveal new technological or structural possibilities. If these possibilities make functions achievable that were not initially considered, our understanding of what should be achieved may also change. Identifying what needs to be accomplished and exploring how to accomplish it influence one another.</p><p>Considering new functions and structural possibilities may also reveal value that had not previously been recognized. What customers can express as requirements does not necessarily encompass everything that would be valuable to them. There may be value in capabilities that existing devices or procedures cannot provide, including possibilities that people have not even considered achievable.</p><p>However, even when a designer recognizes such value, users may not immediately understand it. If they regard the existing method as the natural way of doing things, it may be difficult for them to imagine what would change with a different approach. This is one reason why it can be meaningful to develop and evaluate prototypes based on explicitly expressed needs alongside prototypes that address latent needs. By comparing actual devices, users may come to recognize value they had not previously considered.</p><p>Recognizing value and realizing that value, however, are different matters. Even when the desired function is clear, we still need to determine what kind of structure can achieve it. Designing something that does not yet exist requires us to translate the necessary functions into a physical structure while also considering whether that structure can actually be realized.</p><p>A product’s structure depends on many elements. Achieving the required functions involves considering shape, dimensions, materials, mechanical properties, manufacturing methods, usability, and numerous other conditions. These conditions are not independent. Changing a dimension may affect strength or stiffness, while changing a material may alter manufacturing methods or production constraints. A change to one element can affect many others connected to it.</p><p>For this reason, finding an appropriate answer for each condition independently is not sufficient. Improving one performance characteristic may reduce another. Conversely, conditions that appear incompatible within one structure may become compatible if the structure itself is changed. We therefore need to consider these interrelationships and identify a structure in which the relevant conditions fall within acceptable ranges and the design works as a whole.</p><p>Another important question is whether the conditions regarded as design constraints are genuinely fixed. Previous design examples or past technological limitations may gradually come to be treated as assumptions that cannot be changed. Yet some of these constraints can be overcome by adopting new technologies or developing the necessary technologies ourselves. Once we identify the conditions that must fundamentally be preserved, the range of possible designs depends in part on what else we recognize as changeable.</p><p>This brings us to the distinction between improving an existing product and designing a new structure.</p><p>When improving an existing product, we can build on functions and structures that have already been established, modifying the parts that need to change. In new design, we must consider what kind of structure could achieve the required functions in the first place. The approach to design therefore also depends on which existing structures can serve as references and how well we understand the conditions that can be changed.</p><p>The distinction is not always clear-cut, however. Even a modification to one part of an existing product may substantially alter its relationships with other elements. Likewise, developing a new product often involves making use of existing technologies and structures. What matters is less how much of the resulting shape is new than how broadly we are willing to reconsider the structures and assumptions involved in achieving the intended functions and value.</p><p>Even when a technically feasible structure has been identified, that alone does not mean the purpose of development has been achieved. We must confirm that the structure actually delivers the intended functions and value. For medical devices, medical benefits and clinical utility are important considerations. Where those benefits affect the use of healthcare resources or medical costs, we must also consider their health economic value.</p><p>Of course, the benefits anticipated by a designer must be distinguished from those that have actually been demonstrated. Prototyping and evaluation are needed to establish technical feasibility, while appropriate testing is required to verify safety and effectiveness. When evaluation results differ from initial predictions, investigating the reasons can deepen our understanding of the structure. In some cases, those findings may also require us to reconsider the functions, requirements, or even the value we originally intended to achieve.</p><p>Seen in this way, understanding the problem, exploring possible structures, assessing feasibility, prototyping, and evaluation are all closely interconnected in development. New information may reveal the possibility of a different structure, while considering a structure may identify questions that require further investigation. Evaluation results may, in turn, change how we understand the original problem or the functions that are needed.</p><p>When describing a development process, we can arrange requirements analysis, design, prototyping, and evaluation in a sequence. However, the thinking involved in creating something new does not necessarily follow that same order. Information gathering, problem understanding, structural exploration, and feasibility assessment influence one another and proceed in parallel. As new information and knowledge become available, both the structures we can consider and our understanding of the problem continue to change.</p><p>This kind of thinking requires more than knowledge of individual technical fields. It also requires an understanding of numerous elements and their interrelationships. Even when considering a structure that does not yet exist, we draw on accumulated knowledge and experience to examine how its elements would interact and how changes to one element might affect the others.</p><p>I understand this kind of thinking in terms of a multilayered and multidimensional cognitive structure. Various kinds of information relevant to design are interconnected, and by dynamically changing the relationships among them, I can consider structures that do not yet exist and assess their potential feasibility.</p><p>To understand what it means to develop something new, I believe we need to examine not only the development process and the individual technologies involved, but also the cognition that connects them.</p><p>What, then, is the difference between possessing a large amount of knowledge and information and having that knowledge organized into an interconnected cognitive structure? In the next chapter, I will examine more closely what it means to perceive the relationships among pieces of information.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eee4aae19f55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-chapter-1-eee4aae19f55">Multilayered and Multidimensional Thinking in Development: Chapter 1</a> was originally published in <a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic">Human–AI Coexistence : Principles for a Symbiotic Future</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multilayered and Multidimensional Thinking in Development: Prologue]]></title>
            <link>https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-prologue-69225f2859a1?source=rss-b54030f2935c------2</link>
            <guid isPermaLink="false">https://medium.com/p/69225f2859a1</guid>
            <category><![CDATA[cognitive-science]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[medical-devices]]></category>
            <dc:creator><![CDATA[Keita SUZUKI]]></dc:creator>
            <pubDate>Sun, 08 Nov 2026 14:01:02 GMT</pubDate>
            <atom:updated>2026-11-08T14:01:02.276Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Structure of Thought</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*6dZM2VcMUorKlHl-MbiudA@2x.jpeg" /></figure><p>Over the years, I have been working through conversations with AI to put into words how I perceive things and think about them. One concept I have used in this effort is what I call a “multilayered and multidimensional cognitive structure.”</p><p>When we think about something, we draw on a wide range of knowledge and information. These do not necessarily exist independently of one another. They are interconnected. Even while considering one issue, we may find ourselves thinking about related matters, or new information may change what we previously thought.</p><p>To explain this kind of thinking in words, we need to organize what we considered and how we reached our judgments into some kind of sequence. Yet thought itself does not necessarily process information and its interrelationships one by one in that order. How to explain this difference is one of the questions I have been exploring.</p><p>One useful way to examine this cognitive structure is through the research and development of medical devices, a field in which I have worked for many years.</p><p>When designing a new medical device, I consider many factors, including its required functions, geometry, materials, mechanical properties, manufacturing methods, and usability. Design is also closely connected to questions about what is needed in clinical practice, what the device and the procedure should ideally be like, and what value the device could provide.</p><p>If we describe these activities as a development process, we might begin by understanding customer requirements, then define the necessary functions, design a structure to achieve those functions, and evaluate whether the design is feasible. In actual design work, however, I do not consider these as separate tasks to be addressed one after another.</p><p>When working on a design, I can visualize the three-dimensional shape and movement of the device almost as though I were watching it in motion. At the same time, I perceive the mechanics involved, material properties, manufacturing constraints, and other factors as an integrated whole, without necessarily translating them into words or images. When I change one element, other related elements change with it, affecting both the feasibility of the overall design and the possibilities for alternative structures.</p><p>What I perceive here is more than individual pieces of information. The relationships themselves are also part of what I recognize: how different elements are connected, and how a change in one affects the others. With these relationships forming a multilayered and multidimensional cognitive structure, I can dynamically vary different conditions while considering multiple possibilities simultaneously.</p><p>This kind of cognition is not limited to medical device design. When we try to understand something, examine a problem, or identify new possibilities, we also work with information and the relationships among its elements. Medical device design provides a useful subject for this discussion because these cognitive processes can be examined in connection with tangible functions, physical shapes, and technical feasibility.</p><p>This cognitive structure is not something that remains fixed once it has formed.</p><p>New knowledge or information can change relationships that we previously understood in a particular way. For example, learning about a new technological possibility may lead us to reconsider a condition we had regarded as a constraint. A structure previously considered infeasible may become a viable option. Furthermore, when what can be achieved changes, our understanding of what should be achieved in the first place may also change.</p><p>These changes do not proceed in only one direction. When new information changes a cognitive structure, problems we had not previously considered or questions requiring further investigation may become apparent. Exploring those problems may reveal new solutions, which can in turn change what information is needed and how existing knowledge is understood. Information gathering, analysis, problem understanding, and solution generation influence one another and proceed in parallel, while the cognitive structure itself continues to be updated.</p><p>There is one important point to keep in mind when explaining this kind of thinking. For clarity, we need to discuss separately aspects that actually function as an integrated whole. However, if we treat these distinctions as independent stages of thought, we risk describing something different from the cognition we are trying to understand. We need to explain the individual functions while also preserving their interconnections and the ways they change simultaneously.</p><p>Through my conversations with AI, I have also been working to formalize this kind of thinking and express it as a set of reasoning procedures for AI under the name SYLON. However, describing human cognition as a sequence of procedures is not the same as reproducing the cognitive structure itself. Humans and AI also process information differently, so we need to consider which functions they may be able to achieve in common and where their differences lie.</p><p>Looking ahead, I believe AI will also become an important partner in expanding human cognitive structures.</p><p>AI can do more than retrieve information or propose solutions to given problems. It can also help connect knowledge from different fields, identify relationships we had not previously recognized, and examine existing assumptions and ways of thinking. New information or hypotheses presented by AI may also help us recognize possibilities we had not considered before.</p><p>As a human cognitive structure changes, the information and analysis we ask of AI also change. In turn, the information and analysis provided by AI may further reshape that cognitive structure, giving rise to new questions and possibilities. Through this interaction, I believe humans and AI may be able to draw on their respective strengths to discover new designs and forms of value that would have been difficult for either to reach independently.</p><p>In this series, I will use medical device research and development as a starting point to examine what a multilayered and multidimensional cognitive structure is, how it forms, how it operates, and how it changes over time. I will also consider how AI might contribute to such a structure and what new possibilities may emerge through collaboration between humans and AI.</p><p>This series is not intended to teach general product development methods or engineering design techniques. Nor am I claiming that my understanding of my own thinking constitutes a scientifically verified explanation of the brain’s information-processing mechanisms. Rather, I aim to describe multilayered and multidimensional cognitive structures and how they function as accurately as possible, drawing on existing design theories and cognitive science where relevant.</p><p>To do so, individual chapters will examine subjects such as the formation of cognitive structures, problem understanding, structure generation, and evaluation. These divisions are made for the purpose of explanation. They do not imply that thought actually proceeds in that sequence. Each chapter will examine a different aspect of the same multilayered and multidimensional cognitive structure, whose elements are interconnected in practice.</p><p>Through this series, I hope to take a fresh look at the thinking I engage in every day and describe its structure and workings in a way that others, including AI, can understand. I also hope that putting these ideas into words will help me deepen my own understanding of cognitive processes I have not previously examined closely.</p><p>I will begin by considering what it means to develop something new.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69225f2859a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic/multilayered-and-multidimensional-thinking-in-development-prologue-69225f2859a1">Multilayered and Multidimensional Thinking in Development: Prologue</a> was originally published in <a href="https://medium.com/human-ai-coexistence-principles-for-a-symbiotic">Human–AI Coexistence : Principles for a Symbiotic Future</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>