I started a new job about two months ago as a senior software engineer at a software product company. After a few assignments that I found to be reasonably scoped to my level of domain experience, I was assigned an assignment that affects altering our application's architectural fundamentals and is, at the same time, rather nondeterministic in nature and has no end in sight. In other words, it will be a long time before I can bring a closure to this assignment. By "nondeterministic" I mean questions like "What color shirt should I wear to the party?" vs. "Should I wear more or less warm clothing to the hiking trip given the weather forecast?", which would be more deterministic.
At this stage of my tenure with the company, I am primarily interested in building an easily quantifiable performance record and by that I mean the number of Jira tickets closed and the number of file revisions associated with my name in the version control system. Therefore, I want to have many small assignments which I can scope and bring closure to and which are more deterministic in nature, offering a clear sense of direction. I want the management to which I do not report directly to have an easily consumable list of closures associated with my name as opposed to having one large project that is still "work in progress" with no end in sight.
I talked with boss today and explained all this to him. I put it in the perspective of my cognitive style and personality type and tried to sell him the idea of assigning me more reasonably scoped tasks of tactical nature and that I can be more productive that way. I really don't want the long scoped assignment. I offered a temporary fix, which is not a long term solution, hoping to inject a pause-able milestone in the project but they want an architecture overhaul. He said that he would have more small assignments for me but will have to dedicate some time each week to this hellish architectural change.
Is there something else I could do to convince the management that I can be far more productive with narrowly scoped tasks as opposed to high level without damaging their perception of me as a developer? I am all about CLOSURE and I am stimulated by having many small quantifiable closures under my belly than working on long projects that involve lots of analysis and planning. I become very nervous when I don't check something in for a long time, thinking that the lack of tangible accomplishment record will put me on a firing list. That and I'm really more of an implementation, tactical guy who prefers instant gratification than a long term planner/designer/analyst. I want to be an implementation programmer who writes code rather than does architectural designs.