{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Anti-Architect","title":"EP 82: Peter Bronsnick of Cushman & Wakefield","html":"","width":"100%","height":180,"duration":3208,"description":"In this episode, Christian is joined by Peter Bronsnick, Executive Regional Director at Cushman & Wakefield, overseeing operations across New Jersey, Pennsylvania, and Delaware. Peter's career story of evolution from hands-on developer and deal maker at SJP Properties to leading one of the most powerful real estate advisory platforms in the country of Cushman & Wakefield. Over his two plus decades in the industry, he has touched on every side of the business, site selection, planning, entitlements, construction, leasing, acquisition, capital markets and marketing. Christian and Peter discuss how a developer’s mindset can sharpen leadership within an advisory powerhouse, what defines successful placemaking today, and his role in some of the region's most transformative projects, including M station in Morristown.\nhttps://www.cushmanwakefield.com\nhttps://theantiarchitect.com/\n0:00 – Christian introduces Peter Bronsnick and his role at Cushman Wakefield\n1:29 – Why developers need to better understand architecture and design\n2:49 – Lessons Peter learned working under Steve Pozycki at SJP Properties\n4:37 – The importance of discipline, preparation, and internal expertise\n5:47 – What frustrates Peter about how architects approach projects\n7:07 – Why the architectural vision doesn’t always translate to real-world use\n8:29 – How client collaboration has evolved in architecture and development\n9:48 – The dangers of overdesign and ignoring budget realities\n11:03 – Finding the balance between creative vision and financial feasibility\n12:07 – Getting all stakeholders at the table from the start\n13:47 – What a perfect architect developer partnership should look like\n15:01 – Why architects need to be comfortable pushing back\n16:11 – How to help architects better understand developer risk and mindset\n18:02 – Why studying failed developments teaches more than studying success\n20:05 – The red flags Peter looks for early in developer relationships\n21:00 – Why architects are...","thumbnail_url":"https://img.transistorcdn.com/ZW5eDuUt1bwb5UhkubWT6UvpLMvmRoByqUMpcbhYG6o/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQ1OTQ4LzE2OTY5/NDk0MjctYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}