The process that we follow at Hashnode is one of the processes in GDD. I personally think it is a great way to follow while re-designing certain parts of the website. Saves time, money and has higher chances of producing good result.

Considering the competitive startups scenario we are in, you cannot take risk of redesigning the whole website out of the blue. Here's what we are following:

• Identifying the features which are not used by many people.
• Analysing the issue.
• Setting a timeframe for redesigning that particular feature.
• Analysing its impact on the whole website.
• Re-developing the feature.
• If the results are good, keep it else revert back to old one.

interesting discussion :-) I think Syed hit the nail on the head with startups... GDD is perfect for startups for many reasons (quick launch, ability to iterate as the business iterates, flexible, etc). However, it's equally as important for scale-ups and mature businesses as well.

In terms of workflow, did you have a specific challenge you were running into? If you're running SCRUM and sprints, GDD is perfect. If not, it can still work, but will be less efficient. Please let me know