Explore the stages of a funnel in IT architecture documentation

How to create outlook signature

when i first started drawing diagrams i would stare at the whiteboard wondering how to get started i would draw a box and then delete it i would then draw the same box again and then delete it again so believe me i know how tricky it is to know where to start when building an architecture diagram but if you remember these tips we will talk about you will start building them like like a pro you see a diagram might look like a bunch of boxes and arrows but it's much more than that knowing what every box stands for is not enough the diagram should convey a message it should tell a story let's take this fuji xt20 for example it's a camera with buttons and dials and screens put ing to a layout i can know exactly what every button does you know here's the shutter button here's how to zoom but there's knowing the function of every button makes me a photographer obviously no but the way these various components are ergonomically laid out helps me pick up on the underlaying message the message of how to properly take a picture the ergonomic layout provides context and a deeper meaning than simply labeling the button of the camera and that same concept applies when building architecture diagrams so before you draw your first box on the page figure out your message if you don't know what your message is well ask yourself what is the value this diagram is providing what is the story i'm trying to tell am i doing a step-by-step migration story a lift and shift migration story and etl extract transform load story if you're having a hard time telling the story try to write it down you know just sometimes when you try to write down an explanation of what you're trying to accomplish and then you see written these words well you will have an easier time building your message when i was learning my way to photography the instructor on youtube didn't explain what every number button dial and handle did in the camera that would have been overwhelming you know to say the least and i would have retained nothing knowing how my brain works instead they showed the necessary pieces to get comfortable with the concept of photography as software engineers we assume the more information the better and we try to pack in information in data dense diagrams but introducing your audience to something without the knowledge you have leaves your diagram looks like hieroglyphics so ask yourself the following questions who is the intended audience of this diagram are they familiar with your domain are they a developer who understand all these technical details and then adapt your diagram to the audience which brings us to the next tip more is better than one we're telling a story remember so have your first diagram sitting the stage building up context building up common and shared understanding with your audience but once you start presenting you will likely get a handful of questions how does this component interact with the main database how will this component be secured where do i transform this message and that's where your second your third or your fourth diagram come into play think of them as companion diagrams that make your story significantly more impactful and easier to understand you can answer security questions with a specific diagram that shows the authentication mechanisms encryption solution data flow and whatnot now going back to the camera analogy this is where you start learning about prime versus zoom lenses the various focal lengths the exposure triangle these are not necessary for taking a picture but you learn pretty quickly that they are needed if you want to be or become a photographer all right two more tips to go but before that if you're new to the channel hi my name is ilyas nice to meet you this channel is all about getting to the cloud and growing in the cloud you know career-wise but also from an architectural point technical point if you like what you see make sure to hit the subscribe and notification bell so you don't miss out on new uploads you don't always have to start at the beginning now that you know your audience and the level of familiarity with your domain you can probably skip a few components and jump ahead in your presentation so you don't board them with stuff they already know i'm gonna go back to my camera again it's safe to assume that in 2022 everyone is familiar with what a jpeg is so no need to explain that in depth or if you were teaching someone to drive a manual transmission you wouldn't show them the steering wheel gas pedal and brake pedal if they already know how to drive an automatic transmission you'd focus on the clutch and you'd focus on the gear shift and the last one in the video is rather simple tip but one that i rarely observe in the majority of diagrams and that's the lack of a legend which i think comes from again assuming that everyone is familiar with the boxes with the arrows and other shapes in the diagram but please don't fall into this trap and add a legend to your diagrams everyone who reads it will thank you for it drawing efficient clear and concise diagrams is not a gift you have to be born with it's something you learn and as with everything practice is required but i'm hoping these tips i learned along the way will help you kick start your diagramming career now if you're curious about how a solutions architect spends their day watch this video when i take you with me on a tour of a day in my life from the first to the last activity of the day and if you want to learn about some of the top cloud careers in 2022 watch this one