A more complete and highly informative overview of the contents of the Feb. 7, 2017 Long Branch Urban Design Guidelines Draft Document is available at the website of Ward 6 Councillor Mark Grimes. We owe thanks to Councillor Grimes for the role that he and his office have played in the initiation and development of the Pilot Project.
I was very pleased to have the opportunity to attend the Long Branch Community Advisory Group Meeting on Feb. 7, 2017 in connection with the Long Branch Urban Design Guidelines Pilot Project.
In subsequent posts I will upload pages from the draft document, that was distributed at the meeting.
This material will also be available online at the City of Toronto website.
I’ll be posting it at the Preserved Stories website as well. The website is a convenient place – one among many – where we can share information.
Click on the photos to enlarge them; click again to enlarge them further
The meeting took place on the evening of Feb. 7, 2016 at the Ken Cox Community Centre adjacent to Colonel Samuel Smith Park and Humber College Lakeshore Campus.
Date: Tuesday, Feb. 7, 2017
Time: 6:30 p.m. to 8:30 p.m.
Place: Ken Cox Community Centre (28 Colonel Samuel Smith Park Drive)
Room: Cafeteria A (located inside Father Redmond Catholic Secondary School)
“This upcoming event,” the organizers informed us in an email, “will be an opportunity for the Long Branch Community Advisory Group to attend a meeting where you can learn more about the ongoing Pilot for the Long Branch Neighbourhoods Guidelines, ask questions and share your comments.”
Highly productive meeting
I found the meeting highly productive. It was set for two hours and it went for two hours.
The first hour was devoted to an overview, by the Guidelines team, of the draft document that has been prepared to date.
In the second half, each of the tables devoted time to a facilitated discussion based on a set of questions, and each table then presented two or three key points, from their discussion, to the group as a whole.
I found the event was well-organized. The discussions that followed were productive and valuable.
I learned a lot, and found that my own views, about a variety of topics, were modified, after I took into account comments from other people at my table. I like it when I learn something new, and change my outlook about things, as a result of focused discussion in which many people share their views.
I look forward to the next steps in development of the Pilot Project.
I will share more information about the meeting tomorrow. It’s now late at night, time to leave it for another day.
But first, I will review the meeting with a focus on the five key elements of a good story, as outlined as previous posts, most recently in one that’s entitled:
I recently made up this formulation, of five elements, after someone asked us, at another meeting that I attended (about another topic), “What makes a good story?”
1. Getting attention
First, you need a hook. There are a lot of lot severances happening in Long Branch. The Committee of Adjustment and the OMB are a cross between Kafka’s “Metamorphosis” and the story of Alice in Wonderland. It’s, like, through the looking glass, That’s your hook. There is a reason for people to have an interest in the story of the Long Branch Urban Design Guidelines Pilot Project.
2. Playing the role
There are several role players here – the Councillor, the Chief Planner, each person from SvN, and the residents of Long Branch.
What was missing, by way of role play, at this meeting, was a microphone and a sound system. You need that, to really get into the role, and it’s my hope that a mic will be available in future. Every event – even a walking event such as a Jane’s Walk – benefits from a mic and a portable amp, or even a stationary amp – as soon as you get more than about 20 people gathered together.
Oh, I forgot, there was a table of developers at the meeting. They have a role to play as well.
To take any story on the road, and get some good production values in place to entertain an audience, a large number of talented people usually need to work together with one or two key people coordinating the creative process.
The high quality of collaboration that is evident with the Pilot Project is a source of inspiration for me. What I have seen to date is highly promising.
There’s a frontstage – the official reality, and the backstage – what happens behind the scenes.
What’s been happening behind the scenes with the Pilot project? What’s the reason that the project hasn’t already been completed? The earlier announced timelines pointed to an Advisory Group meeting in December 2016. The meeting in question took place in February 2017.
What happened in the backstage, to cause the delay?
I don’t know what the reason may be. Third-hand reports don’t interest me. At this stage, I don’t care what the reason is, that accounts for the delay. What matters the most, at this point, is that we met on Feb. 7, 2017.
The frontstage looks good. Members of the Advisory Group have provided initial input on the draft, at the meeting. They will have the opportunity to offer further reflections in the next week of two, as soon as the draft is online at the City of Toronto website. That’s what matters, at this step: studying the draft and getting input from the members of the Advisory Group to SvN.
We don’t know where the Pilot Project will lead. We don’t know where this road leads.
It will mean different things to different people. An element of ambiguity will be built into it, as is the case with any great work of art. There’s an element of suspense, an element of anticipation. All this makes for a great story.
[End of storytelling overview]
The next post in a series about the Guidelines is entitled: