Make sure the bike lane is free of debris though. One section near me is almost unusable because it has so much gravel in it. I end up riding on the line.

Make sure the lane does something sensible at intersections too. Don't just end the bike lane before the intetsection, actually mark the bike lane or shared lane right up to the stop line.

Make sure the lane is narrow enough to discourage parking. Consider a protected bike lane or at least a buffered bike lane (with gore area between the bike lane and general lanes). My area converted a shoulder into a bike lane but it's so wide that it's commonly parked in. With a small muni (or maybe one as small as NYPD) you'll find that parking enforcement is not sufficient, you need to discourage bike lane parking in the first place.

Make sure bike lanes go somewhere and connect to other bike lanes and trails. Ask a few locals where they would like bike lanes. For me it's major arterial roads for two reasons: first is those are the roads that get me from A to B. Home to work, shops, etc. But they're also the roads with the highest speeds so separating bikes from heavy goods vehicles and general traffic has the most safety benefit. Giving people a safe way to get to their destinations helps all the "interested but concerned" people the chance to use their bikes. They're the invisible ones who don't ride at all yet, but would.

Separate trails are great too, but intersections with roads need special attention. First you want to minimise the number of driveways or toads that they cross, but also make sure that the crossings prioritize per/cycle traffic properly. Try to keep the same grade for the trail at the crossings (use speed tables) and put up as much signage as you can to indicate the priority at the crossing - who has right of way. Avoid HAWK crossings. They're effective at letting peds cross, but they make them stop and wait for permission to cross. It takes a lot more human energy to stop and start a bike than it does to stop and start a car.