aleixmorgadas’s avataraleixmorgadas’s Twitter Archive—№ 856

              1. Given a sufficiently big organization, "things" will happen regardless if you consider it a priority or not as a team People need stuff done, and if they find resistance in one place, they will find another to include their needs
                Permalink On twitter.com Twitter logo aleixmorgadas’s avatar ♻️ 1 Retweets ❤️ 2 Favorites Mood +1 🙂
            1. …in reply to @aleixmorgadas
              Sometimes, by adding some work to another team's domain, it causes more harm than good. Yes, you might solve a user's pain, but it created an organizational debt all of a sudden Now the domain is split between two teams and they might not even know that this happened
              Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood -1 🙁
          1. …in reply to @aleixmorgadas
            At first, it looks like it was a good decision, in the long run, you clearly see that it wasn't Information is no longer in one team but in the person that is managing the "user needs", sometimes this is handled by a team that's not even in your business unit Conway's Law hits
            Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood +5 🙂
        1. …in reply to @aleixmorgadas
          Now, the architecture/information/use cases start to either duplicate or diverge fast. Conversations like this start happening: - Wait? someone did this already? do they were aware of this problem? did they take this into account? Everything is on fire
          Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood -2 🙁
      1. …in reply to @aleixmorgadas
        A huge amount of work is needed to convey the systems and make the boundaries between teams clear again. It takes time and effort, the system becomes unstable and you are during a period of time not adding value by making things stable when it's already late
        Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood +2 🙂
    1. …in reply to @aleixmorgadas
      I see two main scenarios, I'm talking about the second. When the org chart hits you hard and there's no communication between teams.
      oh my god twitter doesn’t include alt text from images in their APIoh my god twitter doesn’t include alt text from images in their API
      Permalink On twitter.com Twitter logo aleixmorgadas’s avatar ❤️ 1 Favorite Mood -2 🙁
  1. …in reply to @aleixmorgadas
    How do you prevent this to happen? Should you work on preventing or you should work on allowing change even though it looks like the team boundaries are exceeded?
    On twitter.com Twitter logo aleixmorgadas’s avatar Mood 0
    1. …in reply to @aleixmorgadas
      I have the feeling, not the certainty, aiming to prevent this to happen kills fast flow since you create a bureaucratic approach to start initiatives, permission-based instead of enabling-based collaboration. How are other orgs are dealing with this situation?
      Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood -3 🙁