An Engineer often starts with designing and building a machine or structure, and then plans on finding ways to integrate it with the people’s lives. Architects, on the other hand, start from outlining the user needs and experience, and plan on designing a machine or structure that caters to those needs.
Great architecture doesn’t always mean great performance. Great engineering and performance don’t always mean user friendly. There has to be a balance of the two, and that’s one way to find out how well an idea has been executed.
When I was a university student, for a Software Engineering project we would often start from designing the database which is considered to be the core DNA of an application software, and then we would add piles of code and the user interface (UI) on top of that. The result was something more or less functional but something that only a computer engineer could appreciate! That approach worked because as students we couldn’t afford losing marks if the software didn’t meet the requirements.