Jake Rudin’s Post

15 kick-ass skills that you can remember to highlight in your next interview. You didn't pull all those all-nighters to NOT have some amazing talents.

Architecture Professional Morals #3 *While it's important to maintain professional boundaries, it's crucial to avoid directly telling a client that they "don't understand architecture and engineering." This could damage the professional relationship and hinder effective communication. Instead, focus on fostering a collaborative approach that values the client's input while emphasizing your expertise. Here are some strategies to consider: Educate and Explain: Break it Down: Use clear, simple language to explain complex technical concepts. Avoid jargon and focus on the key points. Visual Aids: Utilize diagrams, sketches, or 3D models to illustrate your ideas and make them easier to understand. Real-World Examples: Share relevant examples of similar projects or building codes to demonstrate the feasibility and practicality of your design choices. Active Listening and Empathy: Listen Attentively: Give the client your undivided attention and actively listen to their concerns and suggestions. Validate Their Feelings: Acknowledge their input and show empathy for their perspective, even if you disagree. Ask Open-Ended Questions: Encourage open dialogue and seek clarification on their specific concerns. Assertive Communication: Set Boundaries: Clearly communicate your role as the design expert and the limitations of the client's input. Use "I" Statements: Express your concerns and opinions assertively, focusing on your professional judgment rather than blaming the client. Offer Alternatives: Present alternative solutions that address the client's concerns while maintaining design integrity. Document Everything: Keep Detailed Records: Maintain a written record of all communications, decisions, and changes made to the project. Consult Contracts: Refer to the project contract to clarify the scope of work, responsibilities, and decision-making authority. Remember, the goal is to find a balance between respecting the client's input and maintaining professional control. By approaching the situation with empathy, clear communication, and a focus on collaboration, you can navigate these challenges effectively.

What's the Cost of Employing an Architect? Hiring an architect is a significant step in bringing your architectural dreams to life, whether it's designing your dream home, renovating a space, or conceptualising a public building. While architects offer invaluable expertise and creative insights, it's crucial to understand the costs associated with employing our services. In this post, we'll delve into the various factors that influence the cost of hiring use as your architect. 1. Architectural Fees: As architects we typically charge fees based on the scope of the project. These fees encompass a range of services, including initial consultations, design development, construction documentation, and project management. The complexity and scale of your project directly impact the cost. Larger and more intricate projects tend to have higher architectural fees. 2. Project Size: The size of your project is a significant determinant of architectural costs. Larger projects generally involve more time, effort, and resources, which naturally leads to higher fees. Smaller projects, on the other hand, may have more affordable architectural costs. 3. Project Duration: The duration of your project directly affects architectural costs. Longer projects with extended design and construction phases will naturally result in higher fees. Architects will invest more time and effort in lengthy projects, which is reflected in the cost. 4. Collaboration: Collaborating with an architect from the early stages of a project can be cost-effective. Architects can provide valuable input in the initial design phases, helping you make decisions that optimize the project's cost, functionality, and aesthetics. Their involvement can lead to savings in the long term. 5. Scope of Work: The range of services an architect provides impacts the cost. Depending on your project's needs, the architect's scope of work may include initial design, construction documents, obtaining necessary permits, and overseeing the construction process. The more services required, the higher the cost will be. When considering architectural services, it's essential to have a transparent discussion about fees, scope, and expectations to ensure a successful and budget-conscious project. Remember that investing in a skilled architect can be the key to achieving your architectural vision. Why not give us a call today to discuss !

The Dos and Don'ts of Approaching Architects DON’T: Underestimate the value of creating genuine and honest relationships. Architects who see you as a friend will be more responsive to your products and suggestions. DO: Know your stuff! This doesn’t just apply to your product, although you certainly should prioritise all those details, too. Your knowledge should extend from your product to competing products, market trends, code updates, preferences and anything in between. You can stay informed about the latest updates on websites, like ArchitectureAU. DON'T: Attempt to control the design process over architects and designers. Respect their autonomy and creative control over their work. Collaboration is essential but, understand that there are many factors to go into the decision-making process and you may not be aware of them all. DO: Communicate primarily via email rather than phone calls. Emails allow architects and designers the time to process information and respond at their convenience. Too many unwanted phone calls can end in the architect never reaching out. Or worse, telling their colleagues also not to call. DON'T: Overwhelm architects and designers with unnecessary automated email updates. Limit communications to essential information, such as the introduction of new products and important technical updates. Too many irrelevant updates may deter architects from engaging with your emails in the future. Think smart about your email communications and use data to understand if the right people are engaging with them. If not, try something new!

Architects: Ever wondered if your IT consultants actually know the tools you use? Spoiler alert: 𝗪𝗲 𝗱𝗼, and sometimes we get our hands dirty with them. A little while ago, a client reached out to us with a wire cleanup and conference room setup dilemma. We could have just bought some generic clips. But where's the fun in that? Instead, we decided to measure the exact size of the wires, hit up Thingiverse.com for some inspiration, and after a few adjustments to the model, we printed out custom wire management clips. Did it save us tons of cash? No - Not really Was the custom fit appreciated? Absolutely So, what's the takeaway? It's not always about the cost savings, sometimes it's; → About the custom solution. → Understanding the tools our clients use. → Going the extra mile. Architects, we've got your back. Ever had a quirky solution that worked wonders for you? Share it in the comments!

Architects: I’m a fraud. Everything I tell you is a lie. Just keep doing what you’re doing. Just kidding 😂 But that’s what a few architects want me to tell you… The same architects that: → just want to be told that everything they’re doing and everything they’ve ever done is perfect. → think the “way it’s always been done” is the only way to get something done. → are now looking to retroactively justify all of their past and current beliefs. Of course, the only lie is the one that you tell yourself. → When I say “Design isn’t your differentiator” that doesn’t mean design doesn’t matter. → When I say that architects don’t get business education, that doesn’t mean that an architecture degree sucks. → When I say “all-nighters are bad” that doesn’t mean you shouldn’t work hard. I get it. I post a lot. And it’s easy to take things out of context. But here’s the deal: → If you’re looking for someone to tell you that all you need is a portfolio of pretty pictures, I’m not your guy. → If you’re looking for someone to tell you that you’re doing everything right, I’m not your guy. → If you’re looking for someone that praises starchitects and tells you to do what they do, I’m not your guy. Basically, if you want to follow someone that just reinforces all of your beliefs and tells you that you shouldn’t change anything and what you’re doing is perfect, then don’t follow me. You won’t like me very much. ✌️ (If you’re looking for that, then there are plenty others that will just tell you what you want to hear. Go follow them instead.) But… If you’re open to change… If you want your ideas challenged… If you’re tired of the way things are… If you want to learn from other industries… If you believe there’s room for improvement… And if you’re focused on getting a little better every day… Then welcome aboard and hey, my name is Tyler 👋 I have a weekly newsletter that 5,000+ ambitious architects read every week. Join for free at Growthitect(dot)com/join 🙂

How to get better at system design when you don’t get enough opportunities at work Do you need to actually design systems end-to-end to improve your system design skills? The short answer is no. Instead, you can take these steps to enhance your understanding: 1. Actively participate in design discussions - Join design meetings within your team. - Ask questions and provide input in areas you’re familiar with. - Engage with colleagues to understand different perspectives. 2. Study existing design documents - Read through design documents available in your team or organization. - Try to grasp the rationale behind specific design decisions. - Analyze how different components interact within the system. 3. Research and deepen your understanding - Identify aspects of design documents you don’t fully understand. - Conduct research to fill those knowledge gaps. By taking these proactive steps in your day-to-day job, you can broaden your understanding of system design if you are not getting much design opportunities.

#How do you measure the success of a design project? There are different ways to measure the success of a design project, depending on the project's goals, scope, and criteria. Some possible steps to measure the success of a design project are: # Review the project scope: Compare the final design package with the initial scope and deliverables of the project. Check if the design meets the requirements and specifications of the client and the target audience. # Evaluate the project specifications: Assess the design package's quality, accuracy, and consistency. Look for any errors, inconsistencies, or deviations from the standards and best practices of design engineering. # Analyze the project budget: Calculate the total cost of the design project and compare it with the planned budget. Identify any overruns or savings and the reasons behind them. # Review client satisfaction: Gather feedback from the client and the end-users of the design. Ask them to rate their satisfaction with the design, the process, and the outcome. Find out what they liked and disliked, and what they would improve or change. # Review team satisfaction: Gather feedback from the design team and the stakeholders involved in the project. Ask them to rate their satisfaction with the collaboration, the communication, and the challenges. Find out what they learned and what they would do differently.

This well-written article is about much more than just ivory tower architects. Skip the author's bullet points; click on the link and read his article in its entirety. This well-written article highlights many important organizational concepts and trade-offs, such as: - Job Roles vs Job Titles (with product managers, project managers, and product owners included in the example) - Generalists vs Specialists - Organizational Silos and Friction as a result of of overstaffing, or as a result of enthusiasm in the wrong direction You'll also find links to many other insightful articles from the same author (Alex Ewerlof).

Architects: You have 7 seconds to make a great first impression. So what should you do? 👇 Build rapport. This is where you take time at the beginning of your conversation to NOT talk about business. Instead, talk about life. Do some research ahead of time to understand the person(s) that you’re meeting with. → What do they like and dislike? → What are their hobbies? → Where did they grow up? Find a commonality. And start the conversation there. → Ask a question. → Talke about your commonality. → Share a laugh together. This gets everyone comfortable before you dive into business. And it will ABSOLUTELY make you a more likable architect 🙂 --- ✍️ What’s your favorite way to build rapport?