Wittij Consulting’s Post

Architects: Here are 6 powerful questions that will drive your conversations beyond surface level. 𝟬𝟭 // 𝗪𝗵𝗮𝘁 𝗺𝗮𝗱𝗲 𝘆𝗼𝘂 𝘄𝗮𝗻𝘁 𝘁𝗼 𝘀𝗽𝗲𝗮𝗸 𝘄𝗶𝘁𝗵 𝘂𝘀 𝘁𝗼𝗱𝗮𝘆? It can be difficult to identify the best way to start talking business, but I’ve found this question to be effective. 𝟬𝟮 // 𝗖𝗮𝗻 𝘆𝗼𝘂 𝗵𝗲𝗹𝗽 𝗺𝗲 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝘁𝗵𝗲 𝗯𝗶𝗴𝗴𝗲𝘀𝘁 𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲 𝘆𝗼𝘂 𝗮𝗻𝗱 𝘆𝗼𝘂𝗿 {𝘁𝗲𝗮𝗺/𝗳𝗮𝗺𝗶𝗹𝘆/𝗰𝗼𝗺𝗽𝗮𝗻𝘆} 𝗳𝗮𝗰𝗲 𝘄𝗶𝘁𝗵 𝘆𝗼𝘂𝗿 𝗰𝘂𝗿𝗿𝗲𝗻𝘁 𝘀𝗶𝘁𝘂𝗮𝘁𝗶𝗼𝗻? When you spend a healthy amount of time pursuing prospective clients, it’s easy to forget that there’s a struggle and challenge at the foundation of every decision to start a project. Your goal is to find that challenge. 𝟬𝟯 // 𝗛𝗼𝘄 𝗰𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗶𝘀 𝗶𝘁 𝘁𝗵𝗮𝘁 𝘆𝗼𝘂 𝗿𝗲𝘀𝗼𝗹𝘃𝗲 {𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲}? After you’ve spent some time exploring a challenge, this is a great way to understand how important the challenge is to day-to-day operations or long term goals. 𝟬𝟰 // 𝗛𝗼𝘄 𝘄𝗼𝘂𝗹𝗱 𝘆𝗼𝘂𝗿 𝗱𝗮𝘆 𝗹𝗼𝗼𝗸 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝗶𝗳 {𝗰𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲} 𝗱𝗶𝗱𝗻’𝘁 𝗲𝘅𝗶𝘀𝘁? It’s important to understand what a world without the challenge would mean to your prospective client. How will it impact their day-to-day activities? What will it enable them to do that they can’t do now? 𝟬𝟱 // 𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝘆𝗼𝘂 𝗽𝗹𝗮𝗻𝗻𝗶𝗻𝗴 𝘁𝗼 𝗶𝗻𝘃𝗲𝘀𝘁 𝗶𝗻𝘁𝗼 𝘁𝗵𝗶𝘀 𝗽𝗿𝗼𝗷𝗲𝗰𝘁? This is meant to replace “What’s your budget?” which is my least favorite question of all time. 𝟬𝟲 // 𝗜𝘀 𝘁𝗵𝗲𝗿𝗲 𝗮𝗻𝘆𝘁𝗵𝗶𝗻𝗴 𝗲𝗹𝘀𝗲 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸 𝘄𝗲 𝘀𝗵𝗼𝘂𝗹𝗱 𝗸𝗻𝗼𝘄? It’s difficult to cover everything in the brief conversations that precede proposals. This gives them a chance to fill you in on anything that they think is important. What are your favorite questions to ask?

Highly recommend

There are scorecards with which we evaluate a job well done. Engineers have a different scorecard than an architect, as they should. The trouble begins when an architect uses the same scorecard to evaluate her work. An engineer’s scorecard measures precision, functionality, and efficiency. It's about meeting specifications, ensuring stability, and optimising performance. And perhaps more, I wouldn't know! For an architect, the scorecard should include creativity, beauty, and the emotional impact of the space. It's about how a building feels, how it interacts with its environment, and how it serves people. When architects use an engineer’s scorecard, they risk losing the essence of what makes their work unique. They might achieve perfect functionality, but usually the expense of beauty. We have to recognize that different fields require different measures, and honoring those differences is what leads to distinct work. When you can’t tell the difference between something built by an architect and something built by an engineer, that’s when you know there’s been a mix-up in the scorecard. Architecture is in the details.

Architects: being easy to work with is a hugely underrated growth hack. Nobody likes working with “difficult” people. It’s mentally and emotionally draining. So be easy. Here’s how: Here’s a simple truth: → The smoother the collaboration, the smoother the project. → The smoother the project, the happier the client. → The happier the client, the happier the architect. → The happier the architect, the better the work. → The better the work, the more happy clients. And so on… So what makes an architect easy to work with? → Clear communication → Realistic expectations → Attention to detail → Positive energy → Great listening → Humility Avoid being the architect who is hard to reach or resistant to input. Strive to be the architect everyone looks forward to working with. Prompt in your communications. Generous in sharing credit. Open to feedback. Clients will love working with you. Employees will love working for you. And you’ll attract the best of both. --- ✍🏻 What do you think? ♻️ Repost if this is helpful

5 Tips To Get An Architecture Job From An Online Post

5 Tips To Get An Architecture Job From An Online Post

5 Tips To Get An Architecture Job From An Online Post

6 Mistakes to Avoid When Hiring an Architect 🚩 1. Assuming the Architect with the Highest Fees is the Best Choice. 2. Listening to Negative Reviews Without Verifying Their Authenticity. 3. Thinking an Architect's Education is the Only Measure of Their Competence. 4. Hiring the First Architect You Meet Without Proper Evaluation. 5. Not Considering the Architect's Compatibility with Your Project's Needs. 6. Expecting the Architect to Handle Every Aspect of the Project Alone. Avoid these common mistakes and carefully evaluate potential architects based on these factors, you increase your chances of finding the right professional to bring your project to life successfully.

Someone asked me, What would I tell my younger self? I won't tell anything to my younger self! You know why? You have lot of time than you think you have! You don't have so much time that you assume to have! Time is relative. One can neither change the past nor predict the future! Just live the moments you ve got in hand! Do whatever you can and that which is in your control! So, I won't spend time trying to think what I would tell my younger self! 🤗 Rather, I would do things that I can do now! So that after few years I won't have to think what I would like to tell myself of today! So currently I am building "The Architects Helpline" through dehub for Architects! An online space that solves the problems Architects face in Practice, career, education, business and life! If you are an Architect or designer and have a problem, let us know and we shall have the solutions on the Architects helpline! #dehubforarchitects #architectSSR #ArchitectsHelpline

It is one thing TO THINK you can do it, and it is a totally different thing TO KNOW you can do it! 💡   P R A C T I C E 🎯   An architect does true architecture only about 3% of her time. The rest is technical leading, detailed technical design, and active process leading, which all define the architect's role.   The opportunities to do true architecture are rare. Maybe two to five in one's career. You need a proven track record, experience and recommendations, for someone to trust you with the architecture of a really complex and large system.   So as an architect or an aspiring architect you need to PRACTICE. When the opportunity arises you need to be ready. You need to know that you can do it. You need to be confident, so you can convince others that you can lead the project to success.   You cannot learn on the job. It is not enough time. You cannot try things on the job, because if they don't work you end your chances to get another opportunity. You need to apply things that you know that work. Things you've tried out before or you've seen them working in similar contexts.   Practice on past projects. Just practice. Old projects are like dead bodies in doctors' practice. You know everything about the your old projects. Practice different system designs, different approaches, different methods. Design them in a another way and test if those designs hold water.   It will be a valuable exercise.