There is hardly any difference between Scrum and LeSS as long as number of team is less than 8 and not moving to LeSS Huge. Since there is not much noticeable difference and if you don't tell team about LeSS, team will not even notice that they are adopting Large-Scale Scrum (LeSS). Though better is to conduct workshops to ensure team know about objective behind LeSS and challenges is adoption. Though there is hardly any difference in structure but still LeSS adoption takes time and required lots of effort and energy. LeSS is too simple and usually simple framework become more challenging than complex framework.
Learnt the areas where LeSS adoption takes more time while working as coach with one the biggest recruitment firm having offices across globe. I am working with one product team as of now and there are 3 more products. Highlighting some of the areas where adoption takes more time.
Definition of Product - Team of more than 40 people working on different component, enhancement, production support, testing and requirement management etc. These team has also named their team based on component that they are developing. These teams are having dependencies to each other and can't move their work in production until every team is not ready with their work. They are also having multiple product owner and separate product backlog. Defining product and aligning every team with single product is challenging work. Although senior management understood what I am trying and got full cooperation but still its taking time.
Single product but multiple product owner - This is because product definition was missing. This issue was identified earlier and management was working even before I joined them. Now There is only one product owner and product owner focus more on prioritization rather than clarification. Some challenges are still there and we are working on.
Component team to Feature team - This is the toughest part. Change in culture, mindset, attitude everything needed but still if team is practicing scrum and already self-managed and self-governed then it will be easy. But truth is littler bitter because there is hardly any true self-managed and self-directed, cross-functional team and same here as well. Tester not part of development team because they don't have full-time work, middle layer service integration team is not part of development team, database and configuration management people out of team so essentially only software developers are there that too component-wise. Working with team and designing cross-functional team is going on and hoping to have little matured team in next 4-5 sprints. If this happen then will start working with 2nd product team.
Above all applicable to the organization already practicing Scrum for last 2 years and team understand concept of single scrum team.