Sometimes when project teams are looking for ways to make a MVP (most valuable/viable product) as easy and feasible within constraints they'll choose to opt out of using various features or capabilities and say they'll bring it in in future phases.
My experience has been that future phases tend to be put off 2-3 years down the road and or forgotten all together, pretty quickly.
While this is the client's choice to skip functionality for perceived savings in time, I also aim to make sure they're clear on exactly what it is they are taking out of the solution. In this case I used a three-legged stool metaphor to highlight the impact of not using the Digital Asset Management (DAM) functionality in a MVP, knowing how search was going to be implemented in the near term.
