Iterative development processes that champion prioritizing work and deciding what to do every two weeks can be just as disastrous as planning a year of work in advance. Sure, a business landscape can change in a year, but it rarely changes meaningfully in the span of two weeks.
Set your objectives based on what’s worthwhile before you dive into a project. And set a reasonable duration that matches what makes the project worthwhile. Don’t blindly stick to a cadence of constraining objectives to two weeks intervals. You’ll find yourself in a game of hot potato. Use two week increments or iterations if it better helps you achieve the objective at hand. But don’t force objectives into two week intervals.