Edvance DSA’s Post

61% vote miscommunication as the biggest blocker during design. During last week’s design validation lunch-and-learn, we asked you for the most common reason designs don't work. The audience voted: • 61% miscommunication • 31% outdated information • 8% clashes with existing infrastructure Do these insights match your experience? During the lunch and learn, we covered how teams use Sensat to communicate complex technical using a holistic project view. Leave a comment to receive the session recording. #designvalidation #infrastructure

🚀 New Video Alert: Kickstart Your System Design Journey! 🚀 If you're interested in diving into System Design but unsure where to begin, my latest video breaks it all down. 🌟 In this guide, I cover the essentials, starting with one solid resource that will help you build a strong foundation in the basics of system design. Whether you're a developer, aspiring architect, or just curious about how large-scale systems work, this video is crafted to get you moving in the right direction. Check it out and take the first step toward mastering system design! 💡 👉 https://lnkd.in/gk6mpkDV #SystemDesign #TechEducation #SoftwareEngineering #LearningJourney #DeveloperTips

Planning a Design System Generation: How to approach a cycle sweeping change across a library Post #2 in a series on @medium https://lnkd.in/eJJB8wvt

I'm ecstatic to share that I finished the System Design course. I delved into the complicated process of developing scalable systems, and I came away with fresh perspectives and a deeper understanding of the value of effective design. which inspired me to think about creative solutions and optimised structures 💡. I am eager to apply this knowledge to future projects🚀. #ProfessionalGrowth #ContinuousLearning #SystemDesign

99% of design systems I see don’t focus on: Consistency across all platforms Easy-to-use documentation Seamless handoff between design and development Too much complexity. Not enough simplicity. #designsystems

What are Enterprise Elements? 🔵🟢🔴 #EDGY includes a simple but rich and expressive visual language of only four elements that can be universally used across design challenges/disciplines. The simplicity of this language is important for helping all connected disciplines use these elements and connect their designs. The elements allow us to describe what an enterprise consists of, and how they form a whole by exploring their interrelations and interplay. We use them to describe relevant parts of the enterprise and to design changes to the enterprise and new configurations, so we can communicate potential futures and enable transformation. There are four generic base elements to describe what is happening in an enterprise and its ecosystem: 🙋 People: The individuals co-creating the enterprise or using products. ⚪ Outcome: A result or change that occurs within our enterprise or its ecosystem. ➡️ Activity: What is being done or going on in our enterprise or its ecosystem. ⬜ Object: A structure that is relevant to the enterprise. For more info check out the comments! ____________________________________________ #intersection #enterprisedesign

In my view, guiding questions contribute well to understanding and developing concepts. Therefore, here is a short set of guiding questions, which can be further expanded if needed: 1. People: “Which people are involved in the enterprise or benefit from it?” 2. Outcome: “What outcomes from the enterprise create value?” 3. Activity: “What activities take place in our enterprise or its ecosystem?” 4. Object: “What objects are used in activities?” Interaction and Transformation: “How do people, outcomes, objects, and activities interact to enable transformation?” These questions provide a possible starting point to understand the individual elements of an enterprise and analyze their roles within the overall context. A set of guiding questions is essential to understand and design concepts. What guiding questions would you ask?

What are Enterprise Elements? 🔵🟢🔴 #EDGY includes a simple but rich and expressive visual language of only four elements that can be universally used across design challenges/disciplines. The simplicity of this language is important for helping all connected disciplines use these elements and connect their designs. The elements allow us to describe what an enterprise consists of, and how they form a whole by exploring their interrelations and interplay. We use them to describe relevant parts of the enterprise and to design changes to the enterprise and new configurations, so we can communicate potential futures and enable transformation. There are four generic base elements to describe what is happening in an enterprise and its ecosystem: 🙋 People: The individuals co-creating the enterprise or using products. ⚪ Outcome: A result or change that occurs within our enterprise or its ecosystem. ➡️ Activity: What is being done or going on in our enterprise or its ecosystem. ⬜ Object: A structure that is relevant to the enterprise. For more info check out the comments! ____________________________________________ #intersection #enterprisedesign

Join us for an immersive workshop in Architectural Katas led by the renowned Ted Neward where you'll have the chance to hone your skills in architecting software systems! Fred Brooks once said, "How do we get great designers? Great designers design, of course." But what about architects? Great architects architect! In this workshop, you deep dive into: 🔍 Formulating architectural visions for real-world business problems 💡 Asking the right questions to better understand requirements 🛡️ Defending your technology and approach choices 🔄 Evaluating others' efforts and learning from their perspectives Check out our website for more details and register now to craft great software together! 😍💡

How to consolidate multiple design systems