I think it's important, if you're the smartest person on the team, to view your role as serving the team.
I try to adopt this attitude, I love creating some machinery / abstraction / tool etc to more effectively express the solution to some business problem, but I recognise that my fellow developers must be empowered by any such machinery. I spike, educate if needed, then pair to reimplement. I also try to leave a 'back door' to reversing out of a new design, to let the old way and the new way compete in their minds - which is actually better for them. If the old way wins, I might lick my 'wounds' and try something smaller/simpler.
I try to adopt this attitude, I love creating some machinery / abstraction / tool etc to more effectively express the solution to some business problem, but I recognise that my fellow developers must be empowered by any such machinery. I spike, educate if needed, then pair to reimplement. I also try to leave a 'back door' to reversing out of a new design, to let the old way and the new way compete in their minds - which is actually better for them. If the old way wins, I might lick my 'wounds' and try something smaller/simpler.