Don't focus on criticism, focus on making a very clear value proposition why a change is necessary. For anything. Offering people value is a lot more persuasive than telling why you're right, be it CMS / staffing changes / anything.
That said, I use Drupal quite a lot. For content intensive stuff, it is simply my hammer to seeing a nail.
Re-inventing a CMS seems like a bad idea also. Using a CMS for a non-CMS project also seems like a bad idea. Perhaps enquire with the PM why they suggested Drupal/a CMS? There might be an angle in the project's direction or specification you're missing.
Comments
Don't focus on criticism, focus on making a very clear value proposition why a change is necessary. For anything. Offering people value is a lot more persuasive than telling why you're right, be it CMS / staffing changes / anything.
That said, I use Drupal quite a lot. For content intensive stuff, it is simply my hammer to seeing a nail.
Re-inventing a CMS seems like a bad idea also. Using a CMS for a non-CMS project also seems like a bad idea. Perhaps enquire with the PM why they suggested Drupal/a CMS? There might be an angle in the project's direction or specification you're missing.