Task force splits over whether to fix code or change the policy process

Members debated two approaches: tackle specific code provisions that add cost and delay — "low-hanging fruit" — or take a broader view to change how policies are scoped and reviewed before they become code. One participant said the task force should avoid overreach without council direction.

"I don't feel comfortable having this conversation without the rest of council giving that direction," the member said, arguing that expanding the group's remit into policy-making might go beyond the task force's original intent.

Others countered that compiling examples of costly code provisions and proposing process checkpoints (scoping reviews, stakeholder validation, trade-off analyses) would produce actionable recommendations for council and staff. Several members suggested a small, facilitated subgroup prepare a prioritized agenda and questions for the consultant, rather than attempting wholesale policy changes in the full group.

The group agreed to assemble candidate items for the consultant and to test whether a focused subgroup could produce a clearer agenda for the larger task force to consider.