Skip to main content
The Workplace

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 4
    You don't say what your position is - are you a department head, or a line developer? Truth be told, I think you're stuck either way - management has already blown $100,000 on this, and will now be chasing that investment down the hole and they don't seem to have listened to any technology recommendations before. If you and your team go against this, they will likely replace you with people who "know" that engine.
    – HorusKol
    Commented Apr 6, 2017 at 22:30
  • There is a gap between learning the language (and the engine) and properly used it, usually training is really good for the 1st, not often for the second... Personnaly unless you have some people that will learn the language and engine on their free time and formed other people, I'll just run away.
    – Walfrat
    Commented Apr 7, 2017 at 7:47
  • There's the "sunk money" fallacy. Just because they blew $100,000, that money is gone. The rational question is: Would you use that software if it was free to you, or would that free software cost you more money in inconveniences?
    – gnasher729
    Commented Apr 8, 2017 at 13:45
  • Sorry for the delayed replies: • I'm a group lead. • The gap between training and proficiency is one that i don't think is being considered. (I'm open to learning whatever i need to learn so long as the appropriate training and time is supplied) • If the software were free we wouldn't use it as we already have capabilities in two other similar products.
    – Reahreic
    Commented Apr 11, 2017 at 18:48
  • Following on to gnasher729, every manager learns about Sunk Costs in Management 101 and then promptly forgets about it forever. Maybe approach it from a risk perspective. Unproven technology, unfamiliar engine, high risk of bugs. If you can lead them through the implications of using this thing vs keeping the existing engine like a salesperson, and sell them what they already have, you can dwarf that 100k investment vs the cost and schedule impacts of using it. They could lose over 10x that much. Prove that to them and they may change their minds.
    – MarkTO
    Commented Oct 12, 2018 at 22:05