Sure. Only that's entirely not what the article says. It says not to focus on details _too early_. Because while the entire team may (or may not) agree on the general idea, getting into the details at the same time will take _much_ longer, with very little gain (since that early in the project it may not even be sure if that detail will even be relevant later on). Get the rough ideas sorted out first. Then chip down, iteration by iteration. Finally, get to the details (and then it's time to pay attention to those).