My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Council - 04/12/2022
Ramsey
>
Public
>
Agendas
>
Council
>
2022
>
Agenda - Council - 04/12/2022
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/14/2025 2:28:11 PM
Creation date
4/14/2022 1:44:20 PM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Council
Document Date
04/12/2022
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
260
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Mayor Kuzma replied there is a plan that Council has been following, so it boils down to if the <br /> Council wants to change the direction being taken. <br /> Councilmember Musgrove agreed but thought it would be valuable to have a conversation about <br /> the specifics and the direction they would go. <br /> Councilmember Riley commented Council hasn't talked about it but he would be concerned if <br /> City Council had a meeting first that a consensus may be reached before getting the input of the <br /> Planning Commission. He thought a Council conversation could happen afterward to see what <br /> direction they want to take. <br /> Councilmember Specht suggested not doing it before a Planning Commission meeting. <br /> Councilmember Howell agreed with Councilmember Musgrove that there may be specific items <br /> they want to come away with in that meeting. She didn't want to have all the decisions made <br /> before the joint meeting but to have an idea of what they want to accomplish because if that hasn't <br /> been decided as a Council, the conversation could wander. <br /> Councilmember Riley replied Council could suggest an agenda or as individuals they could <br /> highlight what they think the questions are. He continued Staff may have a good idea of what the <br /> questions are and Council could adjust. He agreed a good agenda is important to guide the <br /> discussion. <br /> Mayor Kuzma asked Deputy City Administrator/Community Dev. Director Hagen if that is <br /> something he could come back to Council with, follow-up questions to get the discussion started. <br /> Councilmember Musgrove commented she was okay having the other meeting first but she would <br /> like to have the order or agenda, the direction, coming from Council and not the Planning <br /> Commission. She stated Council didn't have to have all the ideas but if Council could have it <br /> structured in such a way as to have input, which is where a good agenda is important, as with <br /> strategy meetings, which are inclusive but have a set structure with goals and outcomes. <br /> City Administrator Ulrich thought it would be valuable to have a meeting with just the Council to <br /> set the agenda, to frame the discussion, ask the pertinent questions, and lay those out in detail. <br /> That could be shared with the Planning Commission in advance, schedule the meeting with no <br /> time limitations, and have an open discussion with that framework. He suggested scheduling the <br /> meeting around the time the planning manager starts. <br /> Councilmember Woestehoff agreed that the goal of tonight is to say there are two issues, the <br /> MUSA boundary, and also the COR framework. He thought if there was a good agenda, the two <br /> topics could be done in one meeting, if time wasn't limited by another meeting directly following. <br /> He stated if they were doing just the MUSA boundary he would be comfortable doing that ahead <br /> of the Planning Commission because he thought talking about MUSA wouldn't go more than 90 <br /> minutes to get feedback and direction. He liked the idea of treating it more like a strategy session. <br /> City Council Work Session/March 22, 2022 <br /> Page 3 of 11 <br />
The URL can be used to link to this page
Your browser does not support the video tag.