{"id":1399,"date":"2025-04-04T15:17:02","date_gmt":"2025-04-04T15:17:02","guid":{"rendered":"https:\/\/pawelopitek.com\/?p=1399"},"modified":"2025-04-28T19:59:26","modified_gmt":"2025-04-28T19:59:26","slug":"the-middleman-effect","status":"publish","type":"post","link":"https:\/\/pawelopitek.com\/en\/blog\/media-en\/the-middleman-effect\/","title":{"rendered":"The Middleman Effect"},"content":{"rendered":"

[et_pb_section fb_built=”1″ admin_label=”section” _builder_version=”4.16″ global_colors_info=”{}”][et_pb_row admin_label=”row” _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ sticky_enabled=”0″]<\/p>\n

\n

A Hopeful Beginning<\/h2>\n

I didn\u2019t immediately notice that something was wrong<\/strong>.
\nAt first, everything seemed well-organized: clear division of responsibilities<\/strong>, transparent agreements<\/strong>, and mutual trust<\/strong>.<\/p>\n

My role was to create a website using materials provided by the client.
\nThe partner \u2014 the intermediary \u2014 was responsible for communication<\/strong>, keeping the schedule on track<\/strong>, and managing information flow<\/strong>.<\/p>\n

In theory \u2014 an ideal setup.
\nIn practice \u2014 step by step, the boundaries of my work began to blur.<\/em><\/p><\/blockquote>\n

First came minor delays<\/strong>, then shifting requirements<\/strong>, and finally \u2014 direct expectations that went far beyond what we had agreed upon initially<\/strong>.<\/p>\n

This story taught me more<\/strong> than any project management handbook ever could.<\/p>\n

And today I know that not every collaboration that starts with a handshake and the words “trust me” should even start at all.<\/em><\/p>\n<\/section>\n

\n

Clear Assumptions<\/h2>\n

At the beginning, everything seemed clear<\/strong>.
\nThe project had defined boundaries<\/strong>, specific needs<\/strong>, and a clear scope<\/strong>.<\/p>\n

My task was to build a website consisting of a dozen or so individual pages plus a portfolio section, all based on a single, repeatable template.<\/p>\n

The assumption was simple:<\/strong> the client would deliver all content and materials, and I would structure the site after receiving all texts and images<\/em>.<\/p>\n

The dynamic portfolio was supposed to follow a clear pattern:
\neach entry would include the same types of data:<\/p>\n

    \n
  • a photo,<\/li>\n
  • a title,<\/li>\n
  • a description,<\/li>\n
  • basic information.<\/li>\n<\/ul>\n

    Straightforward, transparent, without unnecessary complications.<\/em><\/p>\n

    We also agreed on one revision round<\/strong> \u2014 after project completion \u2014 to keep the process smooth and efficient without unnecessary extensions.<\/p>\n

    The division of roles was also clearly outlined.
    \nThe intermediary was to support communication with the client, ensuring that all decisions were conveyed and implemented on schedule.<\/p>\n

    My focus was to be on what I do best:
    \ndesigning<\/strong>, structuring content<\/strong>, and building a functional, aesthetic website<\/strong>.<\/p>\n

    Everything was well thought-out.
    \nEverything was documented.
    \nEverything was… until it wasn\u2019t.<\/p><\/blockquote>\n<\/section>\n

    \n

    Early Signs That Something Was Going Wrong<\/h2>\n

    The first signs that the project was starting to derail<\/strong> appeared sooner than expected.
    \nThe materials that were supposed to be provided before layout work began never arrived<\/strong>.<\/p>\n

    Then the intermediary relayed a new client expectation<\/strong>:
    \nhe wanted to see the site’s layout first, so he could know what content to write and how much would be needed.<\/p>\n

    This was a major shift.<\/strong>
    \nInstead of building the site based on finalized content, I had to design the layouts “in the dark”<\/em> \u2014 relying solely on intuition, experience, and a general sense of what might fit.<\/p>\n

    I structured the layouts to be:<\/p>\n

      \n
    • logical,<\/li>\n
    • clear,<\/li>\n
    • suited to the client\u2019s industry.<\/li>\n<\/ul>\n

      I also prepared:<\/p>\n

        \n
      • sample headings,<\/li>\n
      • short introductory texts,<\/li>\n
      • suggested section layouts.<\/li>\n<\/ul>\n

        Everything was designed to help the client fill the site without much effort.<\/p>\n

        We clearly agreed:<\/strong> the client would adapt their content exactly to the provided structure.<\/p>\n

        And once again \u2014 theory is one thing, practice another.<\/em><\/p>\n

        In many places, the client couldn\u2019t deliver texts that matched the planned sections.
        \nI had to discard entire modules and layout parts<\/strong>.<\/p>\n

        The time I spent designing, refining, and optimizing them \u2014 was lost<\/em>.<\/p>\n

        Moreover, the sample texts I had created as mere examples were almost entirely accepted as final website content.<\/p><\/blockquote>\n

        Preparing those samples required:<\/p>\n

          \n
        • not only writing,<\/li>\n
        • but also market research,<\/li>\n
        • competitive analysis,<\/li>\n
        • and strategic communication planning.<\/li>\n<\/ul>\n

          Normally, such work is the job of a copywriter and business consultant<\/strong> \u2014 priced separately and highly.<\/p>\n

          In this project, that work was absorbed into the original pricing<\/em> without any additional compensation.<\/p>\n

          This was one of those moments<\/strong> where I clearly saw how easily a small change in scope could turn into many hours of extra work<\/strong> \u2014
          \nhours that were neither planned nor accounted for<\/em> in the original estimate.<\/p>\n<\/section>\n

          \n

          A Project That Kept Growing Endlessly<\/h2>\n

          While I tried to manage the initial changes, new ones appeared<\/strong>.
          \nThe originally agreed number of subpages \u2014 used for pricing \u2014 started doubling<\/strong>.<\/p>\n

          Each new section, each divided piece of content meant:<\/p>\n

            \n
          • more layout work,<\/li>\n
          • more design decisions,<\/li>\n
          • more elements to optimize,<\/li>\n
          • more content to structure and SEO-optimize.<\/li>\n<\/ul>\n

            These were not minor tweaks.<\/strong>
            \nThey were new subpages<\/strong> \u2014 each requiring its own layout, design process, and execution time.<\/p>\n

            Portfolio \u2014 From Simplicity to Chaos<\/h3>\n

            The portfolio<\/strong> became an even bigger challenge.<\/p>\n

            The initial plan was very specific:<\/p>\n

              \n
            • each project would have a title<\/strong>,<\/li>\n
            • one video<\/strong>,<\/li>\n
            • six photos<\/strong>.<\/li>\n<\/ul>\n

              It was supposed to be repeatable and easy to implement through a single dynamic template.<\/p>\n

              In practice, however, things quickly got complicated.<\/em><\/p>\n

              It turned out that not every project had a video<\/strong>.
              \nI had to create a conditional display mechanism<\/strong> \u2014 ensuring the layout remained clean whether a video was present or not.<\/p>\n

              Photo Galleries \u2014 an Endless Challenge<\/h3>\n

              The photo galleries<\/strong> became an even greater challenge.<\/p>\n

              Instead of six photos per project:<\/p>\n

                \n
              • some projects had two photos,<\/li>\n
              • some had six,<\/li>\n
              • some had as many as twenty-six.<\/li>\n<\/ul>\n

                Each such case required:<\/p>\n

                  \n
                • adjusting the dynamic gallery layout,<\/li>\n
                • ensuring proper and aesthetic display,<\/li>\n
                • maintaining layout consistency regardless of photo count.<\/li>\n<\/ul>\n

                  These adjustments \u2014 seemingly small \u2014 meant huge amounts of extra work<\/strong>:<\/p>\n

                    \n
                  • creating new display rules,<\/li>\n
                  • testing responsiveness,<\/li>\n
                  • optimizing performance for larger galleries,<\/li>\n
                  • manually checking the appearance of every project page.<\/li>\n<\/ul>\n

                    Once again \u2014 all this extra work was done outside the original scope and without additional compensation.<\/p><\/blockquote>\n

                    I did my best to rescue the project and maintain high quality,
                    \nbut it became increasingly clear<\/strong> that the gap between the initial assumptions and reality<\/strong> had grown too wide to ignore.<\/p>\n<\/section>\n

                    \n

                    A Lesson I Had to Learn<\/h2>\n

                    Looking back on this project, I clearly see how small shifts in assumptions<\/strong> can turn a well-planned collaboration into a series of misunderstandings and mounting difficulties<\/strong>.
                    \nBut I also see something more<\/em>.<\/p>\n

                    Most of the decisions that introduced chaos and extra work didn\u2019t come directly from the client<\/strong>.
                    \nIn many cases, it was the intermediary<\/strong> who, with the best intentions, promised the client full flexibility \u2014 without consulting me about the consequences or the impact on the agreed scope<\/em>.<\/p>\n

                    I understand that the intentions were good<\/strong>.
                    \nI understand that the desire to satisfy the client<\/strong> can sometimes overshadow practical realities.<\/p>\n

                    But that\u2019s why I now know how crucial it is that every change must be discussed and agreed upon beforehand<\/strong>, with full awareness of its consequences.<\/p>\n

                    I have great respect<\/strong> for the cooperation and the person I worked with.<\/p>\n

                    That’s why I believe it\u2019s even more important to draw conclusions<\/strong>:<\/p>\n

                      \n
                    • set clear communication rules,<\/li>\n
                    • clearly define responsibilities,<\/li>\n
                    • establish specific work accounting rules.<\/li>\n<\/ul>\n

                      Because professional collaboration isn’t just about completing a project.
                      \nIt\u2019s also about mutual respect for each other\u2019s time, effort, and commitment.<\/p><\/blockquote>\n<\/section>\n

                      \n

                      A New Standard for Collaboration<\/h2>\n

                      This project taught me more<\/strong> than I expected at the start.<\/p>\n

                      I realized how critically important precise arrangements<\/strong> are:<\/p>\n

                        \n
                      • not just the scope of work,<\/li>\n
                      • but also communication methods,<\/li>\n
                      • the change approval process,<\/li>\n
                      • and responsibility for decisions along the way.<\/li>\n<\/ul>\n

                        I learned that even the best intentions<\/strong> \u2014 if not supported by clear rules \u2014 can lead to:<\/p>\n

                          \n
                        • misunderstandings,<\/li>\n
                        • unintentional overload,<\/li>\n
                        • and frustration.<\/li>\n<\/ul>\n

                          Today, I know that every collaboration<\/strong>, whether direct with a client or through an intermediary, must be built on the same foundations:<\/p>\n

                            \n
                          • respect for time<\/strong>,<\/li>\n
                          • respect for agreements<\/strong>,<\/li>\n
                          • mutual responsibility for the project<\/strong>.<\/li>\n<\/ul>\n

                            I don’t regret this lesson<\/strong>.
                            \nOn the contrary \u2014 I see it as an investment in the future<\/em>.<\/p>\n

                            Because every experience, even a difficult one, brings me closer to building better, healthier, and more satisfying collaborations.<\/p><\/blockquote>\n

                            And it is on these principles that I want to base all future projects.<\/strong><\/p>\n<\/section>\n

                            [\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"

                            What happens when a project no longer feels like a collaboration? Discover how good intentions, unclear roles, and shifting expectations can derail even the best plans.<\/p>\n","protected":false},"author":2,"featured_media":1322,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[5],"tags":[59,60],"class_list":["post-1399","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-media-en","tag-client-relationships","tag-project-management"],"_links":{"self":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/posts\/1399","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/comments?post=1399"}],"version-history":[{"count":0,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/posts\/1399\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/media\/1322"}],"wp:attachment":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/media?parent=1399"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/categories?post=1399"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/tags?post=1399"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}