As long as everyone on your team is working with the same vocabulary and expectations, it doesn't really matter a whole lot.
A scenario that could be harmful is when someone says, "let's skip the design" and then sees somebody spending a bunch of time on something they define as "the design".
So, just have a light convo with your team along the lines of, "When you say skip the design, here's what still needs to happen and here's what to expect."
Usually this solves all/most semantic confusion. I've been there though. At the end of the day, you're all working towards the same goal of shipping something useful/useable and time is money–so spending time arguing over what is and what isn't design is not productive.